Network · data from 2026-11-12
AS5630 WORLDLINE-GERMANY Worldline SA
Registry name: WORLDLINE-GERMANY Worldline SA, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS5630, 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.
| 89.106.184.0/22 | Valid | Nonecovered by 89.106.184.0/21 | 0 0%low visibility |
| 89.106.188.0/22 | Valid | Nonecovered by 89.106.184.0/21 | 0 0%low visibility |
AS-SET
AS5630 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 13 are in fix.csv.
- Route object: none2
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 89.106.184.0/22 | No route object for it. A route object for 89.106.184.0/21 with origin AS5630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5630 in the RIR database for the space. |
| Route object: none | 89.106.188.0/22 | No route object for it. A route object for 89.106.184.0/21 with origin AS5630 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5630 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS5630 whose prefix no peer sees AS5630 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.106.184.0/21 | RIPE | Valid |
| 89.106.184.0/24 | RIPE | Valid |
| 89.106.185.0/24 | RIPE | Valid |
| 89.106.186.0/24 | RIPE | Valid |
| 89.106.187.0/24 | RIPE | Valid |
| 89.106.188.0/24 | RIPE | Valid |
| 89.106.189.0/24 | RIPE | Valid |
| 89.106.190.0/24 | RIPE | Valid |
| 89.106.191.0/24 | RIPE | Valid |
| 2a01:20::/48 | RIPE | Valid |
| 2a01:20:4::/48 | RIPE | Valid |
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.