Skip to main content

AS206548

TLAP-ZCOM

ZCOM.cz s.r.o

Registry

Authoritative registration data

AS number
206548
Name
TLAP-ZCOM
Organisation
ZCOM.cz s.r.o
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS206548
185.178.172.0/22 IPv4 /22 not checked
185.201.232.0/22 IPv4 /22 not checked
185.250.232.0/22 IPv4 /22 not checked
45.81.96.0/22 IPv4 /22 not checked
5.182.148.0/22 IPv4 /22 not checked
2a0a:6580::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS206548
Address families
NIX.CZ: Public peering VLAN 100,000 Mbps IPv4 · IPv6
Peering.cz 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS206548 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS206548 in AS paths

Observed upstreams
Families
AS39392 SuperNetwork 304 1,242
v4 v6
AS16019 VODAFONE-CZ-AS 44 225
v4 v6
AS6939 HURRICANE 89 223
v4 v6
AS174 COGENT-174 61 74
v6
AS8218 NEO-ASN 5 65
v4
AS24482 SGGS-AS-AP 2 62
v4 v6
AS1764 NEXTLAYER-AS 4 31
v4 v6
AS20562 OPEN-PEERING-AS 5 30
v4
AS14840 ASN14840 2 30
v4 v6
AS22356 ASN22356 5 25
v4
AS4455 BSO 2 15
v4
AS6204 ZET-NET 1 5
v4
AS6663 TTI-NET 1 5
v4
AS13194 BITE 1 5
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS206548 in AS paths

Observed downstreams
Families
AS210111 netcraftsolutions 86 127
v4 v6
AS50398 FASTCOMMUNICATIONS 22 29
v6

No rows match “”.

Showing – of

Uncertain adjacencies

16 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.