Network · data from 2026-11-12
AS42353 Simwood eSMS
Registry name: SIMWOOD Simwood eSMS Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42353, 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.
| 207.170.190.0/23 | Invalid: origin | Other origin only | 0 0%low visibility |
| 91.233.5.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 178.22.136.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 178.22.140.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.63.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.22.136.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.63.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.63.143.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.22.136.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.22.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.22.139.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.22.140.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.22.141.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.22.142.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 178.22.143.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.63.142.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 194.0.210.0/24 | Valid | RIR databaseRIPE | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS42353: AS-SIMWOOD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS42353 isn't in the set, or no route object for AS42353 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS42353 in it | Not covered |
|---|---|---|---|---|---|
| AS-SIMWOOD | RIPE5 member sets in no database: AS-198426, AS-31631, AS-45033, AS-DYFEDIT, AS206754:AS-TRANSIT | 61 | 12 | Yes | 1 |
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 11 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- AS-SET: missing member5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 207.170.190.0/23 | ROAs covering it name AS19793, not AS42353. If AS42353 should announce it, add a ROA for AS42353. |
| Route object: none | 207.170.190.0/23 | Route objects for it name AS19793. Add a route object with origin AS42353 in the RIR database for the space. |
| ROA: none | 91.233.5.0/24 | No ROA covers it. Add a ROA for AS42353, maxLength 24. |
| AS-SET: missing member | AS-SIMWOOD | AS-SIMWOOD (RIPE) lists AS-198426; no IRR database read has it. |
| AS-SET: missing member | AS-SIMWOOD | AS-SIMWOOD (RIPE) lists AS-31631; no IRR database read has it. |
| AS-SET: missing member | AS-SIMWOOD | AS-SIMWOOD (RIPE) lists AS-45033; no IRR database read has it. |
| AS-SET: missing member | AS-SIMWOOD | AS-SIMWOOD (RIPE) lists AS-DYFEDIT; no IRR database read has it. |
| AS-SET: missing member | AS-SIMWOOD | AS-SIMWOOD (RIPE) lists AS206754:AS-TRANSIT; no IRR database read has it. |
Route objects not announced
Route objects with origin AS42353 whose prefix no peer sees AS42353 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.22.142.0/23 | RIPE | Valid |
| 185.63.140.0/22 | RIPE | No ROA |
| 2a02:28c8::/32 | 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.