Network · data from 2026-11-12
AS26538 SINGLE-DIGITS - Single Digits, Inc.
Registry name: SINGLE-DIGITS - Single Digits, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26538, 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.
| 75.102.129.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 192.40.106.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 75.102.130.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 199.168.147.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
AS-SET
AS26538 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 8 are in fix.csv.
- ROA: none4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 75.102.129.0/24 | No ROA covers it. Add a ROA for AS26538, maxLength 24. |
| ROA: none | 192.40.106.0/24 | No ROA covers it. Add a ROA for AS26538, maxLength 24. |
| ROA: none | 75.102.130.0/24 | No ROA covers it. Add a ROA for AS26538, maxLength 24. |
| ROA: none | 199.168.147.0/24 | No ROA covers it. Add a ROA for AS26538, maxLength 24. |
Route objects not announced
Route objects with origin AS26538 whose prefix no peer sees AS26538 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.105.98.0/24 | RADB | No ROA |
| 75.102.128.0/24 | ARIN | No ROA |
| 149.84.0.0/16 | NTTCOM | No ROA |
| 199.168.144.0/24 | ARIN | No ROA |
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.