bgpreport

Network · data from 2026-11-12

AS63299 PATHWAYS - Pathways Health and Community Support LLC

Registry name: PATHWAYS - Pathways Health and Community Support LLC, US · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS63299, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63299, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
104.244.48.0/24 No ROA Nonecovered by 104.244.48.0/23 673 100% 67
104.244.49.0/24 No ROA Nonecovered by 104.244.48.0/23 673 100% 67
104.244.50.0/24 No ROA Nonecovered by 104.244.50.0/23 673 100% 67
104.244.51.0/24 No ROA Nonecovered by 104.244.50.0/23 673 100% 67
209.194.93.0/24 No ROA None 673 100% 67

AS-SET

AS63299 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 12 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none104.244.48.0/24No ROA covers it. Add a ROA for AS63299, maxLength 24.673 of 673
Route object: none104.244.48.0/24No route object for it. A route object for 104.244.48.0/23 with origin AS63299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63299 in the RIR database for the space.673 of 673
ROA: none104.244.49.0/24No ROA covers it. Add a ROA for AS63299, maxLength 24.673 of 673
Route object: none104.244.49.0/24No route object for it. A route object for 104.244.48.0/23 with origin AS63299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63299 in the RIR database for the space.673 of 673
ROA: none104.244.50.0/24No ROA covers it. Add a ROA for AS63299, maxLength 24.673 of 673
Route object: none104.244.50.0/24No route object for it. A route object for 104.244.50.0/23 with origin AS63299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63299 in the RIR database for the space.673 of 673
ROA: none104.244.51.0/24No ROA covers it. Add a ROA for AS63299, maxLength 24.673 of 673
Route object: none104.244.51.0/24No route object for it. A route object for 104.244.50.0/23 with origin AS63299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63299 in the RIR database for the space.673 of 673
ROA: none209.194.93.0/24No ROA covers it. Add a ROA for AS63299, maxLength 24.673 of 673
Route object: none209.194.93.0/24No route object for it. Add a route object with origin AS63299 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS63299 whose prefix no peer sees AS63299 announce. Many are kept on purpose (backup routes, space announced only in some places).

104.244.48.0/23RADBNo ROA
104.244.50.0/23RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.