Network · data from 2026-11-12
AS19525 3E-COMPANY - 3E COMPANY ENVIRONMENTAL, ECOLOGICAL AND ENGINEERING
Registry name: 3E-COMPANY - 3E COMPANY ENVIRONMENTAL, ECOLOGICAL AND ENGINEERING, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19525, 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.
| 172.87.230.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS19525 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.
- ROA: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 172.87.230.0/24 | No ROA covers it. Add a ROA for AS19525, maxLength 24. |
Route objects not announced
Route objects with origin AS19525 whose prefix no peer sees AS19525 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.110.145.128/26 | RADB | No ROA |
| 63.251.118.0/24 | RADB | No ROA |
| 70.167.173.0/24 | RADB | Valid |
| 192.58.131.0/24 | RADB | 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.