asn.dev

Observed topology

AS5033 AS5033 - Key Information Systems, Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5033: 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
AS20001Charter Communications IncResidentialIPv4493
AS46887Crown Castle Fiber LLCUnclassifiedIPv4122
AS396998Path Network, Inc.UnclassifiedIPv4118
AS22911SINAP-TIX, LLCUnclassifiedIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS19588GOR CORPORATIONUnclassifiedIPv462
AS394704GOR CORPORATIONUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS20001Charter Communications IncResidentialIPv4615
AS46887Crown Castle Fiber LLCUnclassifiedIPv4122
AS396998Path Network, Inc.UnclassifiedIPv4118
AS19588GOR CORPORATIONUnclassifiedIPv462
AS394704GOR CORPORATIONUnclassifiedIPv460
AS22911SINAP-TIX, LLCUnclassifiedIPv458

Provenance

Where this comes from

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