asn.dev

Observed topology

AS268874 AS268874 - IT Facilities

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268874: 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
AS270417UP Down Telecom LtdaResidentialIPv4 IPv6213
AS268624Gamers Club LtdaUnclassifiedIPv4 IPv6123
AS273814Renato silva almeida e ciaUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269144SILVANET PROVEDOR DE INTERNET LTDAUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS270417UP Down Telecom LtdaResidentialIPv4 IPv6271
AS268624Gamers Club LtdaUnclassifiedIPv4 IPv6123
AS273814Renato silva almeida e ciaUnclassifiedIPv460
AS269144SILVANET PROVEDOR DE INTERNET LTDAUnclassifiedIPv458
AS6939Hurricane Electric LLCTransitIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv62
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv62

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.