asn.dev

Observed topology

AS60672 SC

Hosting RIPE Network Services

Upstreams 4 carry this network
Downstreams 14 this network carries
Adjacent (IPv4) 18
Adjacent (IPv6) 5
Upstream graph Who carries AS60672, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS60672 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60672: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6881
AS2914NTT America, Inc.TransitIPv4 IPv6578
AS48185team.blue NVUnclassifiedIPv420
AS34309Link11 GmbHUnclassifiedIPv48

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS202656Ivanov Vitaliy SergeevichUnclassifiedIPv4 IPv64,818
AS57148Bytehouse LtdUnclassifiedIPv4300
AS201862VMhosts LtdUnclassifiedIPv4245
AS39150HOSTING TELECOM LTDHostingIPv4 IPv6192
AS214056Future Technology Group LtdUnclassifiedIPv4120
AS215089Fast Panda LimitedUnclassifiedIPv4120
AS219250Civo LTDUnclassifiedIPv4120
AS206357Aldermore Bank PLCUnclassifiedIPv475
AS19797DEXAGON Inc.UnclassifiedIPv460
AS48611Cablestreet LtdUnclassifiedIPv460

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS202656Ivanov Vitaliy SergeevichUnclassifiedIPv4 IPv64,818
AS3356Level 3 Parent, LLCTransitIPv4 IPv63,942
AS2914NTT America, Inc.TransitIPv4 IPv63,671
AS57148Bytehouse LtdUnclassifiedIPv4300
AS201862VMhosts LtdUnclassifiedIPv4245
AS39150HOSTING TELECOM LTDHostingIPv4 IPv6192
AS48185team.blue NVUnclassifiedIPv4126
AS214056Future Technology Group LtdUnclassifiedIPv4120
AS215089Fast Panda LimitedUnclassifiedIPv4120
AS219250Civo LTDUnclassifiedIPv4120

Provenance

Where this comes from

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