asn.dev

Observed topology

AS4765 PACIFICINTERNET-AS-AP Pacific Internet Pte Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4765: 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
AS4651National Telecom Public Company LimitedUnclassifiedIPv4 IPv612,307
AS4628Pacific Internet Pte LtdUnclassifiedIPv4 IPv61,429
AS45430SBN-IIG/AWN-IIG transit providerUnclassifiedIPv4 IPv61,334
AS24482SG.GSHostingIPv4 IPv622

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134826Softde'but Co.,LTD.UnclassifiedIPv465
AS58690Internet East Co., Ltd.UnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4651National Telecom Public Company LimitedUnclassifiedIPv4 IPv612,419
AS4628Pacific Internet Pte LtdUnclassifiedIPv4 IPv61,430
AS45430SBN-IIG/AWN-IIG transit providerUnclassifiedIPv4 IPv61,348
AS134826Softde'but Co.,LTD.UnclassifiedIPv465
AS58690Internet East Co., Ltd.UnclassifiedIPv464
AS24482SG.GSHostingIPv4 IPv622
AS45642Jasmine International TowerUnclassifiedIPv42

Provenance

Where this comes from

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