Observed topology

AS11870 ALTICOR-INC - ALTICOR INC

Unclassified ARIN Enterprise

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

Upstream graph Who carries AS11870, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS11870 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11870: 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.

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	771
AS3356	Level 3 Parent, LLC	Transit	IPv4	301
AS7018	AT&T Enterprises, LLC	Residential	IPv4	244
AS4628	Pacific Internet Pte Ltd	Unclassified	IPv4	128
AS17439	NTT COMMUNICATIONS INDIA NETWORK SERVICES PRIVATE LIMITED	Hosting	IPv4	122

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS55571	No. 43000,	Unclassified	IPv4	19

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	771
AS3356	Level 3 Parent, LLC	Transit	IPv4	301
AS7018	AT&T Enterprises, LLC	Residential	IPv4	244
AS4628	Pacific Internet Pte Ltd	Unclassified	IPv4	147
AS17439	NTT COMMUNICATIONS INDIA NETWORK SERVICES PRIVATE LIMITED	Hosting	IPv4	122
AS55571	No. 43000,	Unclassified	IPv4	19

Provenance

Where this comes from

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