Network · data from 2026-11-12
AS34949 INTERPC-AS IDLINE SAS
Registry name: INTERPC-AS IDLINE SAS, FR · not in PeeringDB
69IPv4 routes
100.0% RPKI valid · 89.9% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
7 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS34949, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS34949, 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.
| 159.100.42.0/24 | Valid | Other origin onlycovered by 159.100.32.0/20 | 673 100% |
| 159.100.43.0/24 | Valid | Other origin onlycovered by 159.100.32.0/20 | 673 100% |
| 159.100.44.0/24 | Valid | Other origin onlycovered by 159.100.32.0/20 | 673 100% |
| 159.100.46.0/23 | Valid | Nonecovered by 159.100.32.0/20 | 671 100% |
| 185.60.24.0/24 | Valid | Nonecovered by 185.60.24.0/23 | 671 100% |
| 185.60.25.0/24 | Valid | Nonecovered by 185.60.24.0/23 | 671 100% |
| 185.60.26.0/24 | Valid | Nonecovered by 185.60.26.0/23 | 671 100% |
| 109.239.112.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.112.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.113.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.116.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.116.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.117.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.118.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.118.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.119.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.122.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.122.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.123.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.124.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.125.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.126.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.239.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.32.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.32.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.33.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.34.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.34.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.35.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.38.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.38.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.39.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.40.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.40.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.41.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 159.100.46.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.60.24.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.60.26.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.85.224.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.85.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.85.225.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.85.226.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.85.226.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.85.227.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.48.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.48.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.49.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.50.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.50.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.51.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.52.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.52.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.53.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.54.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.54.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.55.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.56.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.56.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.57.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.58.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.58.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.59.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.60.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.60.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.61.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.62.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.62.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.112.63.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS34949 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 14 are in fix.csv.
- Route object: none7
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 159.100.42.0/24 | Route objects for it name AS47160. A route object for 159.100.32.0/20 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
| Route object: none | 159.100.43.0/24 | Route objects for it name AS47160. A route object for 159.100.32.0/20 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
| Route object: none | 159.100.44.0/24 | Route objects for it name AS47160. A route object for 159.100.32.0/20 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
| Route object: none | 159.100.46.0/23 | No route object for it. A route object for 159.100.32.0/20 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
| Route object: none | 185.60.24.0/24 | No route object for it. A route object for 185.60.24.0/23 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
| Route object: none | 185.60.25.0/24 | No route object for it. A route object for 185.60.24.0/23 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
| Route object: none | 185.60.26.0/24 | No route object for it. A route object for 185.60.26.0/23 with origin AS34949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34949 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34949 whose prefix no peer sees AS34949 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.239.112.0/20 | RIPE | No ROA |
| 159.100.32.0/20 | RIPE | No ROA |
| 185.60.24.0/22 | RIPE | No ROA |
| 185.85.224.0/22 | RIPE | No ROA |
| 217.112.48.0/20 | RIPE | No ROA |
| 217.112.56.0/22 | RIPE | No ROA |
| 217.112.60.0/22 | RIPE | No 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.