bgpreport

Network · data from 2026-11-12

AS44821 One Op

Registry name: ONEOP Koesio Nord Ouest SAS, FR · PeeringDB

7IPv4 routes 42.9% 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
2Route objects not announced registered with origin AS44821, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44821, 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.
149.86.172.0/22 No ROA Other IRR onlyRADB 670 100% 68
5.253.132.0/23 No ROA RIR databaseRIPE 670 100% 68
5.253.134.0/24 No ROA RIR databaseRIPE 670 100% 68
185.23.138.0/23 No ROA RIR databaseRIPE 670 100% 68
85.118.52.0/22 Valid RIR databaseRIPE 670 100% 68
185.148.252.0/22 Valid RIR databaseRIPE 670 100% 68
185.240.157.0/24 Valid RIR databaseRIPE 670 100% 68

AS-SET

AS44821's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none149.86.172.0/22No ROA covers it. Add a ROA for AS44821, maxLength 22.670 of 673
Route object: RIR149.86.172.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none5.253.132.0/23No ROA covers it. Add a ROA for AS44821, maxLength 23.670 of 673
ROA: none5.253.134.0/24No ROA covers it. Add a ROA for AS44821, maxLength 24.670 of 673
ROA: none185.23.138.0/23No ROA covers it. Add a ROA for AS44821, maxLength 23.670 of 673

Route objects not announced

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

5.253.132.0/22RIPENo ROA
2a07:6380::/29RIPEValid

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.