Skip to main content

AS199490

INTERCONNECT

--------------------------------------------------

Registry

Authoritative registration data

AS number
199490
Name
INTERCONNECT
Organisation
--------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS199490
185.14.232.0/22 IPv4 /22 not checked
45.84.164.0/22 IPv4 /22 not checked
2a02:f000::/32 IPv6 /32 not checked

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 AS199490
Address families
NIX.CZ: Public peering VLAN 25,000 Mbps IPv4 · IPv6
Peering.cz 50,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 AS199490 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS199490 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 385 553
v4 v6
AS39392 SuperNetwork 305 535
v4 v6
AS209810 NETCORESERVICES 62 106
v4
AS8218 NEO-ASN 10 42
v4 v6
AS1764 NEXTLAYER-AS 6 17
v4 v6
AS22356 ASN22356 10 15
v4
AS14840 ASN14840 4 15
v4
AS4455 BSO 4 9
v4
AS6204 ZET-NET 2 3
v4
AS6663 TTI-NET 2 3
v4
AS13194 BITE 2 3
v4
AS20562 OPEN-PEERING-AS 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS199490 in AS paths

Observed downstreams
Families
AS200635 INTERCONNECT 411 572
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

15 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.