Network · data from 2026-11-12
AS275813 AS275813 - CRDSA1334
Registry name: AS275813 - CRDSA1334, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS275813, 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.
| 2804:99ec:1001::/48 | Valid | Other IRR onlyTC | 634 100% |
| 2804:99ec:1003::/48 | Valid | Other IRR onlyTC | 634 100% |
| 2804:99ec:ffff::/48 | Valid | Other IRR onlyTC | 634 100% |
AS-SET
AS275813 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 7 are in fix.csv.
- Route object: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2804:99ec:1001::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:99ec:1003::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:99ec:ffff::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS275813 whose prefix no peer sees AS275813 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:99ec::/32 | TC | Valid |
| 2804:99ec:1002::/48 | TC | Valid |
| 2804:99ec:1004::/48 | TC | Valid |
| 2804:99ec:1005::/48 | TC | 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.