bgpreport

Network · data from 2026-11-12

AS208226 OuiHeberg

Registry name: OUIHEBERG Ouiheberg SARL, FR · PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 60.0% with a route object
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
1Route objects not announced registered with origin AS208226, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS208226, 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.
2a0a:79c0:1000::/44 Valid None 636 100% 67
2a0a:79c0:1400::/44 Valid None 634 100% 67
50.117.3.0/24 Valid Other IRR onlyRADB 673 100% 67
109.176.91.0/24 Valid Other IRR onlyRADB 673 100% 67
82.41.137.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
88.151.197.0/24 Valid RIR databaseRIPE 673 100% 67
141.11.185.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
172.252.236.0/24 Valid RIR databaseARIN, RADB 673 100% 67
185.248.33.0/24 Valid RIR databaseRIPE 673 100% 67
194.87.217.0/24 Valid RIR databaseRIPE 673 100% 67
212.80.192.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.140.164.0/24 Valid RIR databaseRIPE 672 100% 67
45.140.165.0/24 Valid RIR databaseRIPE 672 100% 67
151.242.147.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
194.59.9.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
64.204.142.0/24 Valid RIR databaseARIN, RADB 671 100% 66
5.42.158.0/24 Valid RIR databaseRIPE 670 100% 67
2a06:e881:7000::/44 Valid RIR databaseRIPE 635 100% 67
2a0e:4007:fffe::/48 Valid RIR databaseRIPE 635 100% 67
2a0a:79c0:e00::/44 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS208226: AS-OUIHEBERG. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS208226 isn't in the set, or no route object for AS208226 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS208226 in itNot covered
AS-OUIHEBERG RIPElists itself further down 191525 Yes 2

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

  • Route object: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a0a:79c0:1000::/44No route object for it. Add a route object with origin AS208226 in the RIR database for the space.636 of 636
Route object: none2a0a:79c0:1400::/44No route object for it. Add a route object with origin AS208226 in the RIR database for the space.634 of 636
Route object: RIR50.117.3.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR109.176.91.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2a0f:6284:4210::/48RIPEInvalid: origin

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.