bgpreport

Network · data from 2026-11-12

AS21792 FLAGLERHOSPITALINC - Flagler Hospital, Inc

Registry name: FLAGLERHOSPITALINC - Flagler Hospital, Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21792, 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.
107.0.201.0/24 Valid Other IRR onlyRADB 666 99% 67

AS-SET

AS21792 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 20 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: RIR107.0.201.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

38.118.74.0/23ALTDBNo ROA
38.119.118.0/23ALTDBNo ROA
38.119.120.0/23ALTDBNo ROA
38.119.121.0/24ALTDBNo ROA
66.246.104.0/23ALTDBNo ROA
69.22.144.0/24ALTDBNo ROA
69.31.4.0/22ALTDBNo ROA
69.31.12.0/23ALTDBNo ROA
69.31.24.0/24ALTDBNo ROA
204.157.0.0/24ALTDBNo ROA
204.157.1.0/24ALTDBNo ROA
204.157.6.0/24ALTDBNo ROA
204.157.7.0/24ALTDBNo ROA
204.157.9.0/24ALTDBNo ROA
204.157.10.0/24ALTDBNo ROA
204.157.11.0/24ALTDBNo ROA
204.157.14.0/23ALTDBNo ROA
204.157.36.0/23ALTDBNo ROA
205.234.96.0/22ALTDBNo 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.