asn.dev

Observed topology

AS7533 Savecom International Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9676SaveCom Internation Inc.ResidentialIPv4 IPv65,690
AS7656Taiwan Network Access PointResidentialIPv4 IPv6840

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9676SaveCom Internation Inc.ResidentialIPv4 IPv66,056
AS3491PCCW Global (HK) Ltd.TransitIPv43,211
AS9505Taiwan Internet GatewayUnclassifiedIPv4 IPv62,615
AS7656Taiwan Network Access PointResidentialIPv4 IPv6840
AS9924Taiwan Fixed Network, Telco and Network Service Provider.ResidentialIPv4665
AS4780Digital United Inc.ResidentialIPv4 IPv6405

Provenance

Where this comes from

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