Observed topology

AS4857 TVP-OPERATIONS-COMPANY-AP TVP Operations Company

Unclassified APNIC NSP

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4857: 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
AS174	Cogent Communications, LLC	Transit	IPv4	313
AS6939	Hurricane Electric LLC	Transit	IPv4	276
AS2764	AAPT Limited	Unclassified	IPv4	186
AS49915	Megaport (UK) Limited	Unclassified	IPv4	95
AS24482	SG.GS	Hosting	IPv4	27
AS64073	Vetta Group	Unclassified	IPv4	27
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	25
AS35280	F5 Networks SARL	Hosting	IPv4	15

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS152884	NEP AUSTRALIA PTY LTD	Hosting	IPv4	48

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	313
AS6939	Hurricane Electric LLC	Transit	IPv4	276
AS2764	AAPT Limited	Unclassified	IPv4	234
AS49915	Megaport (UK) Limited	Unclassified	IPv4	95
AS152884	NEP AUSTRALIA PTY LTD	Hosting	IPv4	48
AS24482	SG.GS	Hosting	IPv4	27
AS64073	Vetta Group	Unclassified	IPv4	27
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	25
AS35280	F5 Networks SARL	Hosting	IPv4	15

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.