Network · data from 2026-11-12
AS210542
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210542, 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.
| 51.241.213.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 74.0.27.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 87.83.63.0/24 | Invalid: origin | None | 1 0%low visibility |
| 91.109.40.0/24 | Invalid: origin | None | 1 0%low visibility |
AS-SET
AS210542 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 47 are in fix.csv.
- ROA: origin4
- Route object: none4
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 51.241.213.0/24 | ROAs covering it name AS834, not AS210542. If AS210542 should announce it, add a ROA for AS210542. |
| Route object: none | 51.241.213.0/24 | Route objects for it name AS834. Add a route object with origin AS210542 in the RIR database for the space. |
| ROA: origin | 74.0.27.0/24 | ROAs covering it name AS834, not AS210542. If AS210542 should announce it, add a ROA for AS210542. |
| Route object: none | 74.0.27.0/24 | Route objects for it name AS834. Add a route object with origin AS210542 in the RIR database for the space. |
| ROA: origin | 87.83.63.0/24 | ROAs covering it name AS834, not AS210542. If AS210542 should announce it, add a ROA for AS210542. |
| Route object: none | 87.83.63.0/24 | No route object for it. Add a route object with origin AS210542 in the RIR database for the space. |
| ROA: origin | 91.109.40.0/24 | ROAs covering it name AS834, not AS210542. If AS210542 should announce it, add a ROA for AS210542. |
| Route object: none | 91.109.40.0/24 | No route object for it. Add a route object with origin AS210542 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS210542 whose prefix no peer sees AS210542 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.8.191.0/24 | NTTCOM, RADB | Valid |
| 45.89.150.0/23 | RADB | Valid |
| 62.72.182.0/24 | RADB | Valid |
| 62.112.128.0/20 | RADB | Valid |
| 62.112.128.0/22 | RADB | Valid |
| 62.112.132.0/22 | RADB | Valid |
| 62.112.136.0/22 | RADB | Valid |
| 62.112.140.0/22 | RADB | Valid |
| 77.75.197.0/24 | RADB | Valid |
| 82.152.49.0/24 | RADB | Valid |
| 84.32.21.0/24 | RADB | Valid |
| 108.165.56.0/23 | ARIN, RADB | Valid |
| 141.11.134.0/23 | RADB | Valid |
| 146.103.16.0/23 | RADB | Valid |
| 146.247.109.0/24 | RADB | Valid |
| 149.126.92.0/22 | RADB | Valid |
| 179.61.173.0/24 | RADB | Valid |
| 181.214.33.0/24 | RADB | Valid |
| 181.214.75.0/24 | RADB | Valid |
| 181.214.185.0/24 | RADB | Valid |
| 181.214.250.0/24 | RADB | Valid |
| 181.215.127.0/24 | RADB | Valid |
| 181.215.136.0/24 | RADB | Valid |
| 181.215.148.0/24 | RADB | Valid |
| 181.215.154.0/24 | RADB | Valid |
| 181.215.239.0/24 | RADB | Valid |
| 185.126.134.0/23 | RADB | Valid |
| 185.173.27.0/24 | RADB | Valid |
| 185.179.218.0/23 | RADB | Valid |
| 188.64.104.0/22 | RADB | Valid |
| 188.64.104.0/24 | NTTCOM, RADB | Valid |
| 188.64.105.0/24 | NTTCOM, RADB | Valid |
| 188.64.106.0/24 | NTTCOM, RADB | Valid |
| 188.64.107.0/24 | NTTCOM, RADB | Valid |
| 194.53.142.0/24 | RADB | Valid |
| 2400:3e20:2000::/36 | APNIC | Valid |
| 2400:3e20:3000::/36 | APNIC | Valid |
| 2400:3e20:e000::/36 | APNIC | Valid |
| 2400:3e20:f000::/36 | APNIC | 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.