Network · data from 2026-11-12
AS25694 Atomic Data
Registry name: ATOMIC - Atomic Data LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25694, 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.
| 204.153.244.0/22 | No ROA | Other origin only | 673 100% |
| 64.244.50.0/23 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 64.244.48.0/20 | No ROA | RIR databaseARIN | 671 100% |
| 69.67.16.0/20 | No ROA | RIR databaseARIN | 671 100% |
| 162.219.164.0/22 | No ROA | RIR databaseARIN | 671 100% |
| 199.66.72.0/22 | No ROA | RIR databaseARIN | 671 100% |
| 71.5.104.0/21 | No ROA | RIR databaseARIN | 670 100% |
| 2606:ad00::/32 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS25694: AS-ATOMICDATA-1. 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 (AS25694 isn't in the set, or no route object for AS25694 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 | AS25694 in it | Not covered |
|---|---|---|---|---|---|
| AS-ATOMICDATA-1 | ARIN | 4 | 1 | 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: none8
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.153.244.0/22 | No ROA covers it. Add a ROA for AS25694, maxLength 22. |
| Route object: none | 204.153.244.0/22 | Route objects for it name AS7753. Add a route object with origin AS25694 in the RIR database for the space. |
| ROA: none | 64.244.50.0/23 | No ROA covers it. Add a ROA for AS25694, maxLength 23. |
| ROA: none | 64.244.48.0/20 | No ROA covers it. Add a ROA for AS25694, maxLength 20. |
| ROA: none | 69.67.16.0/20 | No ROA covers it. Add a ROA for AS25694, maxLength 20. |
| ROA: none | 162.219.164.0/22 | No ROA covers it. Add a ROA for AS25694, maxLength 22. |
| ROA: none | 199.66.72.0/22 | No ROA covers it. Add a ROA for AS25694, maxLength 22. |
| ROA: none | 71.5.104.0/21 | No ROA covers it. Add a ROA for AS25694, maxLength 21. |
| ROA: none | 2606:ad00::/32 | No ROA covers it. Add a ROA for AS25694, maxLength 32. |
Route objects not announced
Route objects with origin AS25694 whose prefix no peer sees AS25694 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.84.13.0/24 | RADB | No ROA |
| 2620:116:c000::/44 | 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.