asn.dev

Observed topology

AS16552 DIGICERT - Tiggee LLC

Hosting ARIN

Upstreams 60 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 57
Adjacent (IPv6) 42
Upstream graph Who carries AS16552, and who carries them, drawn as a map up to the transit-free core. 32 exchanges Where AS16552 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 60

Networks observed carrying traffic for AS16552: 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
AS1299Arelion Sweden ABTransitIPv4 IPv62,023
AS2914NTT America, Inc.TransitIPv4 IPv61,266
AS6939Hurricane Electric LLCTransitIPv4 IPv61,111
AS3257GTT Communications Inc.TransitIPv4 IPv6847
AS4637Telstra GlobalUnclassifiedIPv4 IPv6319
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6260
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6197
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6143
AS9002RETN LimitedUnclassifiedIPv4 IPv6128
AS24482SG.GSHostingIPv4 IPv6127

All 60 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12008Vercara, LLCHostingIPv4 IPv68,202
AS397215Vercara, LLCUnclassifiedIPv4 IPv641
AS397213Vercara, LLCUnclassifiedIPv4 IPv619

Adjacency

Adjacent networks

All 64

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

ASNetworkTypeFamiliesPaths seen
AS12008Vercara, LLCHostingIPv4 IPv68,202
AS1299Arelion Sweden ABTransitIPv4 IPv63,811
AS2914NTT America, Inc.TransitIPv4 IPv62,651
AS6939Hurricane Electric LLCTransitIPv4 IPv61,543
AS3257GTT Communications Inc.TransitIPv4 IPv61,328
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6583
AS22652Videotron LteeResidentialIPv4 IPv6346
AS4637Telstra GlobalUnclassifiedIPv4 IPv6328
AS24482SG.GSHostingIPv4 IPv6296
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6260

All 64 adjacent →

Provenance

Where this comes from

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