bgpreport

Network · data from 2026-11-12

AS12807 OAB Orange Business Services SA

Registry name: OAB Orange Business Services SA, FR · not in PeeringDB

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

Announced routes

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

2a01:9940:100::/48 No ROA Nonecovered by 2a01:9940::/32 634 100% 67
2a01:9940:101::/48 No ROA Nonecovered by 2a01:9940::/32 634 100% 68
94.124.128.0/21 No ROA RIR databaseRIPE 672 100% 67
185.63.192.0/22 No ROA RIR databaseRIPE 672 100% 67
185.63.192.0/24 No ROA RIR databaseRIPE 672 100% 67
193.33.36.0/23 No ROA RIR databaseRIPE 672 100% 67
193.33.36.0/24 No ROA RIR databaseRIPE 672 100% 67

AS-SET

AS12807 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 10 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a01:9940:100::/48No ROA covers it. Add a ROA for AS12807, maxLength 48.634 of 636
Route object: none2a01:9940:100::/48No route object for it. A route object for 2a01:9940::/32 with origin AS12807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12807 in the RIR database for the space.634 of 636
ROA: none2a01:9940:101::/48No ROA covers it. Add a ROA for AS12807, maxLength 48.634 of 636
Route object: none2a01:9940:101::/48No route object for it. A route object for 2a01:9940::/32 with origin AS12807 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12807 in the RIR database for the space.634 of 636
ROA: none94.124.128.0/21No ROA covers it. Add a ROA for AS12807, maxLength 21.672 of 673
ROA: none185.63.192.0/22No ROA covers it. Add a ROA for AS12807, maxLength 22.672 of 673
ROA: none185.63.192.0/24No ROA covers it. Add a ROA for AS12807, maxLength 24.672 of 673
ROA: none193.33.36.0/23No ROA covers it. Add a ROA for AS12807, maxLength 23.672 of 673
ROA: none193.33.36.0/24No ROA covers it. Add a ROA for AS12807, maxLength 24.672 of 673

Route objects not announced

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

2a01:9940::/32RIPENo 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.