Network · data from 2026-11-12
AS51918 Cerberus Networks Ltd
Registry name: CERBERUSNETWORKS-AS Cerberus Networks Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51918, 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.
| 92.119.254.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 46.37.32.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.32.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.36.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.40.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.44.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.48.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.52.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.56.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.37.60.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 77.73.170.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 77.73.172.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.224.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.224.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.228.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.232.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.236.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.240.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.244.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.248.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 83.151.252.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.14.208.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.117.236.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 195.10.232.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a01:5d00::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:94c0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS51918: AS-CERBERUSNETWORKS. 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 (AS51918 isn't in the set, or no route object for AS51918 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 | AS51918 in it | Not covered |
|---|---|---|---|---|---|
| AS-CERBERUSNETWORKS | RIPE | 1 | 1 | Yes | 0 |
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 1 are in fix.csv.
- ROA: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.119.254.0/24 | No ROA covers it. Add a ROA for AS51918, maxLength 24. |
Route objects not announced
Every route object with origin AS51918 is announced.
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.