bgpreport

Network · data from 2026-11-12

AS31893 H5COLO - H5 Colo Associates LLC

Registry name: H5COLO - H5 Colo Associates LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31893, 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.
74.113.56.0/21 No ROA Other IRR onlyRADB 673 100% 67
192.110.176.0/20 No ROA Other IRR onlyRADB 673 100% 67
208.86.164.0/22 No ROA Other IRR onlyRADB 673 100% 67
216.117.208.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS31893 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 18 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none74.113.56.0/21No ROA covers it. Add a ROA for AS31893, maxLength 21.673 of 673
Route object: RIR74.113.56.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.110.176.0/20No ROA covers it. Add a ROA for AS31893, maxLength 20.673 of 673
Route object: RIR192.110.176.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.86.164.0/22No ROA covers it. Add a ROA for AS31893, maxLength 22.673 of 673
Route object: RIR208.86.164.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.117.208.0/22No ROA covers it. Add a ROA for AS31893, maxLength 22.673 of 673
Route object: RIR216.117.208.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

12.69.190.0/24RADBNo ROA
65.64.216.0/24RADBNo ROA
162.250.224.0/21RADBNo ROA
162.250.224.0/24RADBNo ROA
162.250.225.0/24RADBNo ROA
162.250.226.0/24RADBNo ROA
162.250.227.0/24RADBNo ROA
208.84.176.0/23RADBNo ROA
208.84.178.0/23RADBNo ROA
209.127.246.0/24RADBNo 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.