Network · data from 2026-11-12
AS40123 R2G Services LLC
Registry name: R2G-2 - Transaction Network Services, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40123, 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.
| 38.133.160.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 204.14.0.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 41.221.210.0/24 | Valid | None | 673 100% |
| 83.126.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.126.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.126.22.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.126.56.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS40123: AS-R2G. 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 (AS40123 isn't in the set, or no route object for AS40123 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 | AS40123 in it | Not covered |
|---|---|---|---|---|---|
| AS-R2G | ARIN | 3 | 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: none2
- Route object: none1
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.133.160.0/24 | No ROA covers it. Add a ROA for AS40123, maxLength 24. |
| Route object: RIR | 38.133.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.14.0.0/21 | No ROA covers it. Add a ROA for AS40123, maxLength 21. |
| Route object: RIR | 204.14.0.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 41.221.210.0/24 | No route object for it. Add a route object with origin AS40123 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40123 whose prefix no peer sees AS40123 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.95.228.0/24 | RADB | No ROA |
| 70.42.70.0/24 | RADB | No ROA |
| 74.120.48.0/22 | RADB | No ROA |
| 83.126.16.0/23 | RIPE | Valid |
| 216.223.46.0/24 | RADB | No ROA |
| 2a00:cc0:8001::/48 | RIPE | Invalid: origin |
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.