Network · data from 2026-11-12
AS3259 EXPERIAN Docapost BPO SAS
Registry name: EXPERIAN Docapost BPO SAS, FR · not in PeeringDB
33IPv4 routes
100.0% RPKI valid · 15.2% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
28 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS3259, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS3259, 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.
| 31.44.208.0/24 | Valid | Nonecovered by 31.44.208.0/22 | 673 100% |
| 31.44.209.0/24 | Valid | Nonecovered by 31.44.208.0/22 | 673 100% |
| 31.44.210.0/24 | Valid | Nonecovered by 31.44.208.0/22 | 673 100% |
| 31.44.211.0/24 | Valid | Nonecovered by 31.44.208.0/22 | 673 100% |
| 31.44.212.0/24 | Valid | Nonecovered by 31.44.212.0/23 | 673 100% |
| 31.44.213.0/24 | Valid | Nonecovered by 31.44.212.0/23 | 673 100% |
| 31.44.216.0/24 | Valid | Nonecovered by 31.44.208.0/20 | 673 100% |
| 31.44.217.0/24 | Valid | Nonecovered by 31.44.208.0/20 | 673 100% |
| 31.44.218.0/24 | Valid | Nonecovered by 31.44.208.0/20 | 673 100% |
| 31.44.219.0/24 | Valid | Nonecovered by 31.44.208.0/20 | 673 100% |
| 194.5.110.0/24 | Valid | Nonecovered by 194.5.108.0/22 | 673 100% |
| 194.5.113.0/24 | Valid | Nonecovered by 194.5.112.0/22 | 673 100% |
| 194.5.114.0/24 | Valid | Nonecovered by 194.5.112.0/22 | 673 100% |
| 194.5.115.0/24 | Valid | Nonecovered by 194.5.112.0/22 | 673 100% |
| 194.5.116.0/24 | Valid | Nonecovered by 194.5.116.0/22 | 673 100% |
| 194.5.119.0/24 | Valid | Nonecovered by 194.5.116.0/22 | 673 100% |
| 194.5.123.0/24 | Valid | Nonecovered by 194.5.120.0/22 | 673 100% |
| 194.5.125.0/24 | Valid | Nonecovered by 194.5.124.0/23 | 673 100% |
| 194.5.108.0/24 | Valid | Nonecovered by 194.5.108.0/22 | 670 100% |
| 194.5.109.0/24 | Valid | Nonecovered by 194.5.108.0/22 | 670 100% |
| 194.5.111.0/24 | Valid | Nonecovered by 194.5.108.0/22 | 670 100% |
| 194.5.112.0/24 | Valid | Nonecovered by 194.5.112.0/22 | 670 100% |
| 194.5.117.0/24 | Valid | Nonecovered by 194.5.116.0/22 | 670 100% |
| 194.5.118.0/24 | Valid | Nonecovered by 194.5.116.0/22 | 670 100% |
| 194.5.120.0/24 | Valid | Nonecovered by 194.5.120.0/22 | 670 100% |
| 194.5.121.0/24 | Valid | Nonecovered by 194.5.120.0/22 | 670 100% |
| 194.5.122.0/24 | Valid | Nonecovered by 194.5.120.0/22 | 670 100% |
| 194.5.124.0/24 | Valid | Nonecovered by 194.5.124.0/23 | 670 100% |
| 31.44.208.0/20 | Valid | RIR databaseRIPE | 669 99% |
| 194.5.108.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 194.5.112.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 194.5.120.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 194.5.124.0/23 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS3259 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 34 are in fix.csv.
- Route object: none28
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.44.208.0/24 | No route object for it. A route object for 31.44.208.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.209.0/24 | No route object for it. A route object for 31.44.208.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.210.0/24 | No route object for it. A route object for 31.44.208.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.211.0/24 | No route object for it. A route object for 31.44.208.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.212.0/24 | No route object for it. A route object for 31.44.212.0/23 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.213.0/24 | No route object for it. A route object for 31.44.212.0/23 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.216.0/24 | No route object for it. A route object for 31.44.208.0/20 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.217.0/24 | No route object for it. A route object for 31.44.208.0/20 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.218.0/24 | No route object for it. A route object for 31.44.208.0/20 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 31.44.219.0/24 | No route object for it. A route object for 31.44.208.0/20 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.110.0/24 | No route object for it. A route object for 194.5.108.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.113.0/24 | No route object for it. A route object for 194.5.112.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.114.0/24 | No route object for it. A route object for 194.5.112.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.115.0/24 | No route object for it. A route object for 194.5.112.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.116.0/24 | No route object for it. A route object for 194.5.116.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.119.0/24 | No route object for it. A route object for 194.5.116.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.123.0/24 | No route object for it. A route object for 194.5.120.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.125.0/24 | No route object for it. A route object for 194.5.124.0/23 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.108.0/24 | No route object for it. A route object for 194.5.108.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.109.0/24 | No route object for it. A route object for 194.5.108.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.111.0/24 | No route object for it. A route object for 194.5.108.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.112.0/24 | No route object for it. A route object for 194.5.112.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.117.0/24 | No route object for it. A route object for 194.5.116.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.118.0/24 | No route object for it. A route object for 194.5.116.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.120.0/24 | No route object for it. A route object for 194.5.120.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.121.0/24 | No route object for it. A route object for 194.5.120.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.122.0/24 | No route object for it. A route object for 194.5.120.0/22 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
| Route object: none | 194.5.124.0/24 | No route object for it. A route object for 194.5.124.0/23 with origin AS3259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3259 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3259 whose prefix no peer sees AS3259 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.44.208.0/22 | RIPE | Invalid: maxLength |
| 31.44.212.0/23 | RIPE | Invalid: maxLength |
| 31.44.220.0/22 | RIPE | Invalid: maxLength |
| 45.156.132.0/22 | RIPE | Valid |
| 194.5.112.0/22 | RIPE | Invalid: maxLength |
| 194.5.116.0/22 | RIPE | Invalid: maxLength |
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.