Network · data from 2026-11-12
AS393942 AS393942 - WiredISP Inc.
Registry name: AS393942 - WiredISP Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393942, 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.
| 82.47.216.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 84.75.11.0/24 | Invalid: origin | None | 2 0%low visibility |
| 212.134.250.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 95.135.135.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 145.223.67.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 167.148.163.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 181.214.21.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 86.110.47.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 89.106.15.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 143.20.91.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 155.117.217.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 164.37.202.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 177.201.223.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 185.131.207.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 187.55.167.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 213.139.225.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 213.145.84.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 45.151.143.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 147.79.60.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 151.242.89.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 205.234.177.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 31.58.69.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 37.1.227.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 45.153.164.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 151.244.199.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 162.33.164.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 194.60.89.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 206.162.255.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 45.66.151.0/24 | Valid | RIR databaseRADB, RIPE | 662 98% |
AS-SET
AS393942 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: origin2
- Route object: none2
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 82.47.216.0/24 | ROAs covering it name AS834, not AS393942. If AS393942 should announce it, add a ROA for AS393942. |
| Route object: none | 82.47.216.0/24 | Route objects for it name AS834. Add a route object with origin AS393942 in the RIR database for the space. |
| ROA: origin | 84.75.11.0/24 | ROAs covering it name AS834, not AS393942. If AS393942 should announce it, add a ROA for AS393942. |
| Route object: none | 84.75.11.0/24 | No route object for it. Add a route object with origin AS393942 in the RIR database for the space. |
| Route object: RIR | 212.134.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS393942 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.