asn.dev

Observed topology

AS4694 IDCF IDC Frontier Inc.

Hosting APNIC Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4694: 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
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv610,657
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv67,491
AS17676SoftBank Corp.MobileIPv4 IPv6663
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6236
AS24482SG.GSHostingIPv4 IPv6236
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4232

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17953BroadBand Security, Inc.UnclassifiedIPv4 IPv6372
AS38658LIQUIDNET ASIA LIMITEDUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv610,937
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv67,550
AS17676SoftBank Corp.MobileIPv4 IPv6731
AS17953BroadBand Security, Inc.UnclassifiedIPv4 IPv6372
AS24482SG.GSHostingIPv4 IPv6246
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6241
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4237
AS38658LIQUIDNET ASIA LIMITEDUnclassifiedIPv459
AS9002RETN LimitedUnclassifiedIPv64

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.