Network · data from 2026-11-12
AS211233 Ronsor-LLC Ronsor LLC
Registry name: Ronsor-LLC Ronsor LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211233, 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.
| 2a06:a005:19ba::/48 | Valid | Nonecovered by 2a06:a005:19b0::/44 | 634 100% |
| 2a0a:6040:8e00::/44 | Valid | Nonecovered by 2a0a:6040:8e00::/40 | 634 100% |
AS-SET
AS211233 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 9 are in fix.csv.
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a06:a005:19ba::/48 | No route object for it. A route object for 2a06:a005:19b0::/44 with origin AS211233 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211233 in the RIR database for the space. |
| Route object: none | 2a0a:6040:8e00::/44 | No route object for it. A route object for 2a0a:6040:8e00::/40 with origin AS211233 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211233 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS211233 whose prefix no peer sees AS211233 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a06:a005:19b0::/44 | RIPE | Valid |
| 2a06:a005:19bb::/48 | RIPE | Valid |
| 2a06:a005:19bd::/48 | RIPE | Valid |
| 2a06:a005:19be::/48 | RIPE | Valid |
| 2a0a:6040:8e00::/40 | RIPE | Valid |
| 2a0a:6040:9300::/40 | RIPE | No ROA |
| 2a0a:6040:9300::/44 | RIPE | 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.