Network · data from 2026-11-12
AS218713 NETCENSUS-AS NETCENSUS LTD
Registry name: NETCENSUS-AS NETCENSUS LTD, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218713, 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.
| 89.30.200.0/24 | Invalid: origin | None | 11 2%low visibility |
| 2a14:7583:efd1::/48 | Valid | None | 635 100% |
| 87.121.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a14:c380:20::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS218713 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 3 are in fix.csv.
- ROA: origin1
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 89.30.200.0/24 | ROAs covering it name AS834, not AS218713. If AS218713 should announce it, add a ROA for AS218713. |
| Route object: none | 89.30.200.0/24 | No route object for it. Add a route object with origin AS218713 in the RIR database for the space. |
| Route object: none | 2a14:7583:efd1::/48 | No route object for it. Add a route object with origin AS218713 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS218713 is announced.
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.