asn.dev

Observed topology

AS33333 OBJX - objx.net, LLC

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33333: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,255
AS174Cogent Communications, LLCTransitIPv4 IPv6141
AS1299Arelion Sweden ABTransitIPv4 IPv6123
AS17048objx.net, LLCHostingIPv4 IPv6100
AS18450WebNX, Inc.HostingIPv4 IPv657

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40193Trit Networks, LLCUnclassifiedIPv4 IPv6625
AS22133Octet Brasil LtdaUnclassifiedIPv464
AS40031Satcom Systems IncorporatedUnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,120
AS40193Trit Networks, LLCUnclassifiedIPv4 IPv6625
AS17048objx.net, LLCHostingIPv4 IPv6200
AS22133Octet Brasil LtdaUnclassifiedIPv4192
AS174Cogent Communications, LLCTransitIPv4 IPv6176
AS1299Arelion Sweden ABTransitIPv4 IPv6154
AS18450WebNX, Inc.HostingIPv4 IPv6107
AS40031Satcom Systems IncorporatedUnclassifiedIPv464

Provenance

Where this comes from

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