asn.dev

Observed topology

AS400212 VERGETEL-GROUP-LLC - VergeTel Group LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS400212: 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
AS835GoCodeIT IncUnclassifiedIPv4 IPv6316
AS53667FranTech SolutionsHostingIPv4 IPv6137
AS400587Ryamer, LLCHostingIPv619

Transit

Downstream networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS213607WORLD FIRST COMMUNICATION LTDUnclassifiedIPv4120
AS400503Dan Smith LLCUnclassifiedIPv4 IPv696
AS401612hueNETUnclassifiedIPv4 IPv695
AS206628Tianyu-ZhuUnclassifiedIPv4 IPv694
AS397730coresdev, LLCUnclassifiedIPv4 IPv685
AS205563Marc GomezUnclassifiedIPv672
AS218472Mynfi Pty LtdUnclassifiedIPv460
AS400945CSB-ASNUnclassifiedIPv459
AS212085Alexander BruegmannUnclassifiedIPv641
AS218776FULLFIBER LTDUnclassifiedIPv636

All 15 downstreams →

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS835GoCodeIT IncUnclassifiedIPv4 IPv6953
AS400587Ryamer, LLCHostingIPv4 IPv6261
AS53667FranTech SolutionsHostingIPv4 IPv6137
AS213607WORLD FIRST COMMUNICATION LTDUnclassifiedIPv4120
AS400503Dan Smith LLCUnclassifiedIPv4 IPv696
AS401612hueNETUnclassifiedIPv4 IPv695
AS206628Tianyu-ZhuUnclassifiedIPv4 IPv694
AS397730coresdev, LLCUnclassifiedIPv4 IPv685
AS205563Marc GomezUnclassifiedIPv672
AS218472Mynfi Pty LtdUnclassifiedIPv460

All 18 adjacent →

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.