Network · data from 2026-11-12
AS50224 AS50224 Network
Registry name: as50224 Ryan So, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50224, 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.
| 2a14:6f45:310::/48 | Invalid: origin | None | 6 1%low visibility |
| 142.248.23.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS50224: AS50224:AS-NETWORK. 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 (AS50224 isn't in the set, or no route object for AS50224 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 | AS50224 in it | Not covered |
|---|---|---|---|---|---|
| AS50224:AS-NETWORK | RIPE2 member sets in no database: AS199746:AS-NEXTSERV, AS203867:AS-CUSTOMERS | 259 | 62 | 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: origin1
- Route object: none1
- AS-SET: missing member2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a14:6f45:310::/48 | ROAs covering it name AS59920, AS200242, not AS50224. If AS50224 should announce it, add a ROA for AS50224. |
| Route object: none | 2a14:6f45:310::/48 | No route object for it. Add a route object with origin AS50224 in the RIR database for the space. |
| AS-SET: missing member | AS50224:AS-NETWORK | AS50224:AS-NETWORK (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
| AS-SET: missing member | AS50224:AS-NETWORK | AS50224:AS-NETWORK (RIPE) lists AS203867:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS50224 whose prefix no peer sees AS50224 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.121.222.0/24 | RADB, RIPE | Valid |
| 94.103.125.0/24 | RADB, RIPE | Valid |
| 192.75.197.0/24 | RADB | Valid |
| 2a07:54c0::/36 | RIPE | No ROA |
| 2a07:54c1::/36 | ALTDB | No ROA |
| 2a07:54c2:b00b::/48 | RIPE | Valid |
| 2a11:3a06::/32 | RADB, RIPE | 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.