Network · data from 2026-11-12
AS267788 AS267788 - IP TECHNOLOGIES S.A.S.
Registry name: AS267788 - IP TECHNOLOGIES S.A.S., CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267788, 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.
| 45.167.251.0/24 | Valid | Nonecovered by 45.167.248.0/22 | 673 100% |
| 45.167.249.0/24 | Valid | Nonecovered by 45.167.248.0/22 | 670 100% |
| 45.167.250.0/24 | Valid | Nonecovered by 45.167.248.0/22 | 670 100% |
| 170.247.0.0/24 | Valid | Nonecovered by 170.247.0.0/22 | 670 100% |
| 170.247.1.0/24 | Valid | Nonecovered by 170.247.0.0/22 | 670 100% |
| 170.247.3.0/24 | Valid | Nonecovered by 170.247.0.0/22 | 670 100% |
| 2803:26c0:8000::/33 | Valid | Nonecovered by 2803:26c0::/32 | 630 99% |
| 170.247.2.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2803:26c0::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 38.4.120.0/22 | Valid | RIR databaseARIN | 670 100% |
| 179.1.137.0/24 | Valid | RIR databaseLACNIC | 669 99% |
| 190.90.79.0/24 | Valid | RIR databaseLACNIC, RADB | 668 99% |
AS-SET
AS267788 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 16 are in fix.csv.
- Route object: none7
- Route object: RIR2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.167.251.0/24 | No route object for it. A route object for 45.167.248.0/22 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: none | 45.167.249.0/24 | No route object for it. A route object for 45.167.248.0/22 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: none | 45.167.250.0/24 | No route object for it. A route object for 45.167.248.0/22 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: none | 170.247.0.0/24 | No route object for it. A route object for 170.247.0.0/22 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: none | 170.247.1.0/24 | No route object for it. A route object for 170.247.0.0/22 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: none | 170.247.3.0/24 | No route object for it. A route object for 170.247.0.0/22 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: none | 2803:26c0:8000::/33 | No route object for it. A route object for 2803:26c0::/32 with origin AS267788 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267788 in the RIR database for the space. |
| Route object: RIR | 170.247.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2803:26c0::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267788 whose prefix no peer sees AS267788 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.167.248.0/22 | RADB | Valid |
| 170.247.0.0/22 | RADB | Valid |
| 2801:15a::/40 | RADB | Valid |
| 2803:26c0::/32 | RADB | Valid |
| 2803:3250:ea02::/48 | LACNIC | Valid |
| 2803:3250:ea04::/48 | RADB | No ROA |
| 2803:cda0::/32 | RADB | 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.