bgpreport

Network · data from 2026-11-12

AS199255 REVE-AS Groupement Interet Economique REVE

Registry name: REVE-AS Groupement Interet Economique REVE, FR · not in PeeringDB

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

Announced routes

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

185.4.248.0/24 Valid Nonecovered by 185.4.248.0/22 673 100% 67
185.4.249.0/24 Valid Nonecovered by 185.4.248.0/22 673 100% 67

AS-SET

AS199255 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 4 are in fix.csv.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none185.4.248.0/24No route object for it. A route object for 185.4.248.0/22 with origin AS199255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199255 in the RIR database for the space.673 of 673
Route object: none185.4.249.0/24No route object for it. A route object for 185.4.248.0/22 with origin AS199255 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199255 in the RIR database for the space.673 of 673

Route objects not announced

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

185.4.248.0/22RIPENo ROA
2a02:6840::/32RIPEValid

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.