Network · data from 2026-11-12
AS48305 Noraina
Registry name: NORAINA-EU Noraina Ltd, IE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48305, 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.
| 91.242.128.0/24 | Valid | Nonecovered by 91.242.128.0/22 | 673 100% |
| 91.242.130.0/23 | Valid | Nonecovered by 91.242.128.0/22 | 673 100% |
| 91.242.133.0/24 | Valid | Nonecovered by 91.242.132.0/22 | 672 100% |
| 91.242.128.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.86.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.148.0.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 91.242.132.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:77e0:3302::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:77e0:3301::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:77e0:4401::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:77e0:5301::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:4400::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS48305: RIPE::AS-NORAINA. 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 (AS48305 isn't in the set, or no route object for AS48305 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 | AS48305 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-NORAINA | RIPE | 2 | 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 8 are in fix.csv.
- Route object: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.242.128.0/24 | No route object for it. A route object for 91.242.128.0/22 with origin AS48305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48305 in the RIR database for the space. |
| Route object: none | 91.242.130.0/23 | No route object for it. A route object for 91.242.128.0/22 with origin AS48305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48305 in the RIR database for the space. |
| Route object: none | 91.242.133.0/24 | No route object for it. A route object for 91.242.132.0/22 with origin AS48305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48305 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48305 whose prefix no peer sees AS48305 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.242.128.0/21 | RIPE | No ROA |
| 91.242.129.0/24 | RIPE | Valid |
| 91.242.130.0/24 | RIPE | Valid |
| 91.242.131.0/24 | RIPE | Valid |
| 2a03:77e0::/32 | 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.