asn.dev

Observed topology

AS19050 TIC-DHHS-INTERIOR

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19050: 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
AS15029U.S. Department of Health & Human ServicesUnclassifiedIPv4 IPv6699

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS70National Library of MedicineUnclassifiedIPv4 IPv63,552
AS26810U.S. Dept. of Health and Human ServicesUnclassifiedIPv4 IPv61,166
AS30387National Institutes of HealthUnclassifiedIPv4708
AS5766Indian Health ServiceUnclassifiedIPv4 IPv6592
AS3527National Institutes of HealthUnclassifiedIPv4 IPv6557
AS13611U.S. Center For Disease Control and PreventionUnclassifiedIPv4124
AS22828United States Food and Drug AdministrationUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS15029U.S. Department of Health & Human ServicesUnclassifiedIPv4 IPv67,530
AS70National Library of MedicineUnclassifiedIPv4 IPv63,552
AS26810U.S. Dept. of Health and Human ServicesUnclassifiedIPv4 IPv61,166
AS30387National Institutes of HealthUnclassifiedIPv4708
AS3527National Institutes of HealthUnclassifiedIPv4 IPv6595
AS5766Indian Health ServiceUnclassifiedIPv4 IPv6592
AS13611U.S. Center For Disease Control and PreventionUnclassifiedIPv4124
AS22828United States Food and Drug AdministrationUnclassifiedIPv4 IPv694

Provenance

Where this comes from

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