Network · data from 2026-11-12
AS202543 AbsCloud
Registry name: AbilixSoft-Sf2016 Mrejitor Ltd, BG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202543, 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.
| 2a0f:3980::/30 | Valid | Nonecovered by 2a0f:3980::/29 | 634 100% |
| 2a0f:3984::/30 | Valid | Nonecovered by 2a0f:3980::/29 | 634 100% |
| 2a0f:c300::/30 | Valid | Nonecovered by 2a0f:c300::/29 | 634 100% |
| 2a0f:c304::/30 | Valid | Nonecovered by 2a0f:c300::/29 | 634 100% |
| 91.148.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.246.168.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.246.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.246.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.246.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.154.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.154.178.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.154.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.154.177.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS202543's PeeringDB record names no 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: none4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a0f:3980::/30 | No route object for it. A route object for 2a0f:3980::/29 with origin AS202543 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202543 in the RIR database for the space. |
| Route object: none | 2a0f:3984::/30 | No route object for it. A route object for 2a0f:3980::/29 with origin AS202543 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202543 in the RIR database for the space. |
| Route object: none | 2a0f:c300::/30 | No route object for it. A route object for 2a0f:c300::/29 with origin AS202543 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202543 in the RIR database for the space. |
| Route object: none | 2a0f:c304::/30 | No route object for it. A route object for 2a0f:c300::/29 with origin AS202543 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202543 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202543 whose prefix no peer sees AS202543 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.154.176.0/22 | RIPE | No ROA |
| 185.227.6.0/24 | RIPE | Valid |
| 185.246.168.0/22 | RIPE | No ROA |
| 2a0f:3980::/29 | RIPE | No ROA |
| 2a0f:c300::/29 | 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.