asn.dev

Observed topology

AS10100 UBSGROUPAG-AS-AP UBS Group AG

Unclassified APNIC

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS10100: 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
AS32787Akamai Technologies, Inc.HostingIPv4 IPv62,695
AS4637Telstra GlobalUnclassifiedIPv4335
AS4657StarHub LtdResidentialIPv4315
AS3491PCCW Global (HK) Ltd.TransitIPv4304
AS2516KDDI CORPORATIONMobileIPv4104
AS4812China Telecom (Group)ResidentialIPv4 IPv683
AS4847China Networks Inter-ExchangeUnclassifiedIPv4 IPv681
AS2914NTT America, Inc.TransitIPv473
AS4808China Unicom Beijing Province NetworkResidentialIPv4 IPv671
AS17621China Unicom Shanghai networkUnclassifiedIPv4 IPv668

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS4410Credit Suisse GroupUnclassifiedIPv4360

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv4 IPv63,037
AS4410Credit Suisse GroupUnclassifiedIPv4360
AS4637Telstra GlobalUnclassifiedIPv4335
AS4657StarHub LtdResidentialIPv4333
AS3491PCCW Global (HK) Ltd.TransitIPv4304
AS2516KDDI CORPORATIONMobileIPv4104
AS4812China Telecom (Group)ResidentialIPv4 IPv683
AS4847China Networks Inter-ExchangeUnclassifiedIPv4 IPv681
AS2914NTT America, Inc.TransitIPv473
AS4808China Unicom Beijing Province NetworkResidentialIPv4 IPv671

All 12 adjacent →

Provenance

Where this comes from

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