Network · data from 2026-11-12
AS402475 DELTA-CONSTRUCTORS - Delta
Registry name: DELTA-CONSTRUCTORS - Delta, PH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402475, 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.
| 103.227.211.0/24 | Valid | Other IRR onlyRADB | 403 60% |
| 103.204.23.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.117.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 31.77.244.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 94.118.201.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 2a04:ca80::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a0c:b140::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a11:2dc0::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a11:37c0::/29 | Valid | RIR databaseRIPE | 631 99% |
| 2a12:200::/29 | Valid | RIR databaseRIPE | 631 99% |
| 96.62.89.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 172.120.34.0/24 | Valid | RIR databaseARIN | 1 0%low visibility |
| 172.121.73.0/24 | Valid | RIR databaseARIN | 1 0%low visibility |
AS-SET
AS402475 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 5 are in fix.csv.
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.227.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402475 whose prefix no peer sees AS402475 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.236.203.0/24 | RIPE | Valid |
| 96.62.76.0/24 | RIPE | Valid |
| 195.35.120.0/24 | RIPE | Valid |
| 217.65.72.0/24 | 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.