asn.dev

Observed topology

AS399768 VER-CT-ASN-01 - Verition Group LLC

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS399768: 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 ABTransitIPv4164
AS6461Zayo BandwidthTransitIPv4146
AS9304HGC Global Communications LimitedHostingIPv462
AS3356Level 3 Parent, LLCTransitIPv453
AS7473Singapore Telecommunications LtdUnclassifiedIPv451
AS4637Telstra GlobalUnclassifiedIPv441
AS10103HK Broadband Network Ltd.ResidentialIPv434
AS3257GTT Communications Inc.TransitIPv426
AS4455IX Reach LtdUnclassifiedIPv416
AS43531BSO Network Solutions SASUnclassifiedIPv42

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4164
AS6461Zayo BandwidthTransitIPv4146
AS9304HGC Global Communications LimitedHostingIPv462
AS3356Level 3 Parent, LLCTransitIPv453
AS7473Singapore Telecommunications LtdUnclassifiedIPv451
AS4637Telstra GlobalUnclassifiedIPv441
AS10103HK Broadband Network Ltd.ResidentialIPv434
AS3257GTT Communications Inc.TransitIPv426
AS4455IX Reach LtdUnclassifiedIPv416
AS43531BSO Network Solutions SASUnclassifiedIPv42

Provenance

Where this comes from

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