Network · data from 2026-11-12
AS197545 Era4-ASN Era4 Limited
Registry name: Era4-ASN Era4 Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197545, 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.
| 2a0c:bbc0::/34 | Valid | Nonecovered by 2a0c:bbc0::/33 | 601 94% |
| 95.36.160.0/20 | Valid | Nonecovered by 95.36.160.0/19 | 1 0%low visibility |
| 95.36.128.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 95.36.128.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 2a0c:bbc0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0c:bbc0::/33 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 95.36.128.0/19 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS197545 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: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a0c:bbc0::/34 | No route object for it. A route object for 2a0c:bbc0::/33 with origin AS197545 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197545 in the RIR database for the space. |
| Route object: none | 95.36.160.0/20 | No route object for it. A route object for 95.36.160.0/19 with origin AS197545 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197545 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197545 whose prefix no peer sees AS197545 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 95.36.144.0/20 | RIPE | Valid |
| 95.36.160.0/19 | RIPE | Valid |
| 2a0c:bbc0:8000::/33 | 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.