AS8400 TELEKOM SRBIJA a.d.
Backbone / NSP · based in Serbia · IPLogs default verdict: Transit / backbone
- ASN
- AS8400
- Name
- TELEKOM SRBIJA a.d.
- Category
- Backbone / NSP
- Country
- Serbia
- IPLogs verdict
- Transit / backbone
- Registry
- RIPE NCC
- Allocated
- 1997-07-29
- PeeringDB
- Yes · 4 fac.
- Proxy backbone
- No
About TELEKOM SRBIJA a.d.
TELEKOM SRBIJA a.d. (AS8400) is registered with RIPE NCC in Serbia and was allocated on 1997-07-29. Self-declared in PeeringDB as a Network Service Provider (transit / backbone). IPLogs treats PeeringDB NSPs as core infrastructure (asn_peeringdb_nsp, zero weight) rather than hosting — large carriers in this bucket also carry residential traffic, so per-IP checks decide the verdict. PeeringDB lists it in 4 facilities.
How IPLogs classifies AS8400
When the detection engine sees an IP that routes through AS8400, it checks three lists: (1) the curated VPN-provider ASN list, (2) the datacenter / hosting ASN list, and (3) the trusted CDN allowlist. Matches produce one of vpn_asn, dc_ip, or no flag respectively. Keywords in the org name (e.g. "vpn", "proxy", "anonym") may also trigger vpn_org_keyword even for unknown ASNs.
Use the ASN as a shortcut when you want to block a whole hosting provider at the edge rather than maintaining a per-IP list.
Authoritative sources for AS8400
Third-party registries where you can verify the announcements, peer relationships, and WHOIS registration for this ASN.
Frequently asked questions about AS8400
+Is AS8400 (TELEKOM SRBIJA a.d.) a VPN, datacenter, or residential network?
IPLogs classifies TELEKOM SRBIJA a.d. (AS8400) as a backbone / nsp network based in Serbia. The default verdict for any IP that routes through this ASN is "Transit / backbone".
+Who operates AS8400 and where is it registered?
TELEKOM SRBIJA a.d. (AS8400) is registered with RIPE NCC, operates in Serbia, was allocated on 1997-07-29. It is listed in PeeringDB across 4 facilities.
+How do I check or block AS8400 traffic?
Send any suspect IP to the IPLogs API — POST https://iplogs.com/v1/check with body {"ip":"<ip>"} — and the response reports the originating ASN plus whether it matched the VPN, datacenter, or CDN lists. To block a whole hosting network at the edge, filter on AS8400 instead of maintaining a per-IP list. Copy-paste recipes for Cloudflare WAF, Nginx, and Stripe Radar are at /guides/block-vpn-traffic.