asn.dev

Observed topology

AS18434 FNIS

Hosting ARIN

Upstreams 8 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 0
Upstream graph Who carries AS18434, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS18434 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18434: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv44,801
AS3356Level 3 Parent, LLCTransitIPv4611
AS174Cogent Communications, LLCTransitIPv4229
AS9498BHARTI Airtel Ltd.MobileIPv4115
AS4826Vocus Connect International BackboneUnclassifiedIPv453
AS4230CLARO S.A.ResidentialIPv437
AS7473Singapore Telecommunications LtdUnclassifiedIPv417
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv43

Transit

Downstream networks

inferred

Networks for which AS18434 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS6419IDD Enterprises, LPUnclassifiedIPv43,780
AS46203Fidelity National Information Services, Inc.UnclassifiedIPv460

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS18434 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv48,733
AS6419IDD Enterprises, LPUnclassifiedIPv43,900
AS3356Level 3 Parent, LLCTransitIPv4629
AS174Cogent Communications, LLCTransitIPv4239
AS9498BHARTI Airtel Ltd.MobileIPv4115
AS46203Fidelity National Information Services, Inc.UnclassifiedIPv460
AS4826Vocus Connect International BackboneUnclassifiedIPv453
AS4230CLARO S.A.ResidentialIPv437
AS7473Singapore Telecommunications LtdUnclassifiedIPv417
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv43

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.