asn.dev

Observed topology

AS263589 AS263589 - MGP TELECOM

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263589: 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
AS14282ONN MULTIMIDIA LTDAResidentialIPv4948
AS262865Ired Internet LtdaResidentialIPv4 IPv6249

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262289Singular Telecom LTDAUnclassifiedIPv4361
AS264520Radioscan Telecom Com. De Compon. Eletr. Ltda-EPPUnclassifiedIPv4183
AS264172CLEBER ATAIDE PASTI & CIA LTDAUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS14282ONN MULTIMIDIA LTDAResidentialIPv41,486
AS262289Singular Telecom LTDAUnclassifiedIPv4361
AS262865Ired Internet LtdaResidentialIPv4 IPv6262
AS264520Radioscan Telecom Com. De Compon. Eletr. Ltda-EPPUnclassifiedIPv4183
AS264172CLEBER ATAIDE PASTI & CIA LTDAUnclassifiedIPv47

Provenance

Where this comes from

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