asn.dev

Observed topology

AS395846 DIRECTCOMID - Direct Communications Rockland, Inc

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS395846: 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
AS6461Zayo BandwidthTransitIPv4 IPv6588
AS3356Level 3 Parent, LLCTransitIPv4 IPv6521
AS15305Syringa Networks, LLCUnclassifiedIPv4 IPv6270

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11252Idaho State UniversityEducationIPv4331
AS399824Infinite Q NetworksUnclassifiedIPv4 IPv696
AS398148MOATiT, LLCUnclassifiedIPv4 IPv681
AS402800TaekniUnclassifiedIPv461
AS397503Nuvek LLC.UnclassifiedIPv460
AS400278TITLE FINANCIAL CORPORATIONUnclassifiedIPv459
AS402304California Casualty Management CompanyUnclassifiedIPv423
AS54345FARM BUREAU MUTUAL INSURANCE COMPANY OF IDAHOUnclassifiedIPv422

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6891
AS3356Level 3 Parent, LLCTransitIPv4 IPv6782
AS15305Syringa Networks, LLCUnclassifiedIPv4 IPv6441
AS11252Idaho State UniversityEducationIPv4331
AS399824Infinite Q NetworksUnclassifiedIPv4 IPv696
AS398148MOATiT, LLCUnclassifiedIPv4 IPv681
AS402800TaekniUnclassifiedIPv461
AS397503Nuvek LLC.UnclassifiedIPv460
AS400278TITLE FINANCIAL CORPORATIONUnclassifiedIPv459
AS402304California Casualty Management CompanyUnclassifiedIPv423

Provenance

Where this comes from

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