bgpreport

Network · data from 2026-11-12

AS219005

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219005, 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.

51.241.203.0/24 Invalid: origin None 2 0%low visibility 1
94.118.82.0/24 Invalid: origin None 2 0%low visibility 1
188.220.250.0/24 Invalid: origin Other origin only 2 0%low visibility 1
188.221.131.0/24 Invalid: origin Other origin only 2 0%low visibility 1
188.221.145.0/24 Invalid: origin Other origin only 2 0%low visibility 1
212.212.26.0/24 Invalid: origin Other origin only 2 0%low visibility 1
188.221.178.0/24 Invalid: origin Other origin only 1 0%low visibility 1
188.220.251.0/24 Invalid: origin Other origin only 0 0%low visibility 1
188.221.191.0/24 Invalid: origin Other origin only 0 0%low visibility 1

AS-SET

AS219005 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 19 are in fix.csv.

  • ROA: origin9
  • Route object: none9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin51.241.203.0/24ROAs covering it name AS834, not AS219005. If AS219005 should announce it, add a ROA for AS219005.2 of 673
Route object: none51.241.203.0/24No route object for it. Add a route object with origin AS219005 in the RIR database for the space.2 of 673
ROA: origin94.118.82.0/24ROAs covering it name AS834, not AS219005. If AS219005 should announce it, add a ROA for AS219005.2 of 673
Route object: none94.118.82.0/24No route object for it. Add a route object with origin AS219005 in the RIR database for the space.2 of 673
ROA: origin188.220.250.0/24ROAs covering it name AS834, not AS219005. If AS219005 should announce it, add a ROA for AS219005.2 of 673
Route object: none188.220.250.0/24Route objects for it name AS834. Add a route object with origin AS219005 in the RIR database for the space.2 of 673
ROA: origin188.221.131.0/24ROAs covering it name AS834, not AS219005. If AS219005 should announce it, add a ROA for AS219005.2 of 673
Route object: none188.221.131.0/24Route objects for it name AS834. Add a route object with origin AS219005 in the RIR database for the space.2 of 673
ROA: origin188.221.145.0/24ROAs covering it name AS834, not AS219005. If AS219005 should announce it, add a ROA for AS219005.2 of 673
Route object: none188.221.145.0/24Route objects for it name AS834. Add a route object with origin AS219005 in the RIR database for the space.2 of 673
ROA: origin212.212.26.0/24ROAs covering it name AS137409, not AS219005. If AS219005 should announce it, add a ROA for AS219005.2 of 673
Route object: none212.212.26.0/24Route objects for it name AS137409. Add a route object with origin AS219005 in the RIR database for the space.2 of 673
ROA: origin188.221.178.0/24ROAs covering it name AS834, not AS219005. If AS219005 should announce it, add a ROA for AS219005.1 of 673
Route object: none188.221.178.0/24Route objects for it name AS834. Add a route object with origin AS219005 in the RIR database for the space.1 of 673
ROA: origin188.220.251.0/24ROAs covering it name AS6079, not AS219005. If AS219005 should announce it, add a ROA for AS219005.0 of 673
Route object: none188.220.251.0/24Route objects for it name AS6079. Add a route object with origin AS219005 in the RIR database for the space.0 of 673
ROA: origin188.221.191.0/24ROAs covering it name AS6079, not AS219005. If AS219005 should announce it, add a ROA for AS219005.0 of 673
Route object: none188.221.191.0/24Route objects for it name AS6079. Add a route object with origin AS219005 in the RIR database for the space.0 of 673

Route objects not announced

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

178.93.17.0/24RADBValid

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.