asn.dev

Observed topology

AS33422 NETC - New England Telehealth Consortium

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33422: 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
AS13536FirstLight Fiber, Inc.ResidentialIPv4757
AS13977FidiumResidentialIPv416
AS174Cogent Communications, LLCTransitIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS40626Wentworth-Douglass HospitalUnclassifiedIPv465
AS47059York HospitalUnclassifiedIPv465
AS53742Houlton Regional HospitalUnclassifiedIPv465
AS54093Eastern Maine Healthcare SystemsUnclassifiedIPv465
AS54181ST JOSEPH HOSPITALUnclassifiedIPv458
AS25750Southwestern Vermont Health Care CorporationUnclassifiedIPv438
AS11350NorthWestern Medical CenterUnclassifiedIPv435
AS13977FidiumResidentialIPv431
AS54471Androscoggin Valley HospitalUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS13536FirstLight Fiber, Inc.ResidentialIPv41,117
AS13977FidiumResidentialIPv4112
AS40626Wentworth-Douglass HospitalUnclassifiedIPv465
AS47059York HospitalUnclassifiedIPv465
AS53742Houlton Regional HospitalUnclassifiedIPv465
AS54093Eastern Maine Healthcare SystemsUnclassifiedIPv465
AS54181ST JOSEPH HOSPITALUnclassifiedIPv458
AS25750Southwestern Vermont Health Care CorporationUnclassifiedIPv438
AS11350NorthWestern Medical CenterUnclassifiedIPv435
AS174Cogent Communications, LLCTransitIPv41

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.