bgpreport

Network · data from 2026-11-12

AS22200 BLOOMINGDALE-COMMUNICATIONS - Bloomingdale Communications Inc.

Registry name: BLOOMINGDALE-COMMUNICATIONS - Bloomingdale Communications Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22200, 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.
38.45.84.0/22 No ROA Other IRR onlyRADB 673 100% 67
63.238.252.0/23 No ROA Other IRR onlyRADB 673 100% 67
65.112.79.0/24 No ROA Other IRR onlyRADB 673 100% 67
154.59.152.0/22 No ROA Other IRR onlyRADB 673 100% 67
198.47.48.0/20 No ROA Other IRR onlyRADB 673 100% 67
199.255.100.0/22 No ROA Other IRR onlyRADB 673 100% 67
208.25.96.0/23 No ROA Other IRR onlyRADB 673 100% 67
216.184.40.0/21 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS22200 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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none38.45.84.0/22No ROA covers it. Add a ROA for AS22200, maxLength 22.673 of 673
Route object: RIR38.45.84.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none63.238.252.0/23No ROA covers it. Add a ROA for AS22200, maxLength 23.673 of 673
Route object: RIR63.238.252.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none65.112.79.0/24No ROA covers it. Add a ROA for AS22200, maxLength 24.673 of 673
Route object: RIR65.112.79.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.59.152.0/22No ROA covers it. Add a ROA for AS22200, maxLength 22.673 of 673
Route object: RIR154.59.152.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.47.48.0/20No ROA covers it. Add a ROA for AS22200, maxLength 20.673 of 673
Route object: RIR198.47.48.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.255.100.0/22No ROA covers it. Add a ROA for AS22200, maxLength 22.673 of 673
Route object: RIR199.255.100.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.25.96.0/23No ROA covers it. Add a ROA for AS22200, maxLength 23.673 of 673
Route object: RIR208.25.96.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.184.40.0/21No ROA covers it. Add a ROA for AS22200, maxLength 21.673 of 673
Route object: RIR216.184.40.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS22200 is announced.

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.