asn.dev

Observed topology

AS46786 IPTRANSIT - IP Transit Inc.

Hosting ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS46786: 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
AS3356Level 3 Parent, LLCTransitIPv4228
AS1299Arelion Sweden ABTransitIPv4203
AS174Cogent Communications, LLCTransitIPv4 IPv6133
AS2914NTT America, Inc.TransitIPv4105
AS6939Hurricane Electric LLCTransitIPv490
AS6696VERIXI SAUnclassifiedIPv411
AS20766Association "Gitoyen"UnclassifiedIPv411
AS24482SG.GSHostingIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206376Intellectica Systems India Private LimitedUnclassifiedIPv4174
AS5577root SAHostingIPv4 IPv630
AS200197HYBRID ADTECH SP.Z.O.O.UnclassifiedIPv48

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4264
AS1299Arelion Sweden ABTransitIPv4259
AS206376Intellectica Systems India Private LimitedUnclassifiedIPv4174
AS174Cogent Communications, LLCTransitIPv4 IPv6170
AS2914NTT America, Inc.TransitIPv4138
AS6939Hurricane Electric LLCTransitIPv4117
AS5577root SAHostingIPv4 IPv673
AS204279Eltrona Interdiffusion S.A.UnclassifiedIPv435
AS24482SG.GSHostingIPv4 IPv622
AS6696VERIXI SAUnclassifiedIPv4 IPv621

All 13 adjacent →

Provenance

Where this comes from

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