Network · data from 2026-11-12
AS198291 Goomobile S.r.l.
Registry name: nextdata Next Data S.r.l, IT · PeeringDB
12IPv4 routes
100.0% RPKI valid · 0.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS198291, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS198291, 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.
| 46.232.136.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 46.232.137.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 46.232.138.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 46.232.139.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 46.232.140.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 46.232.141.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 46.232.143.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 672 100% |
| 185.124.47.0/24 | Valid | Nonecovered by 185.124.44.0/22 | 672 100% |
| 185.124.44.0/24 | Valid | Nonecovered by 185.124.44.0/22 | 670 100% |
| 185.124.45.0/24 | Valid | Nonecovered by 185.124.44.0/22 | 670 100% |
| 185.124.46.0/24 | Valid | Nonecovered by 185.124.44.0/22 | 670 100% |
| 46.232.142.0/24 | Valid | Nonecovered by 46.232.136.0/21 | 669 99% |
| 2a04:dc40::/29 | Valid | RIR databaseRIPE | 630 99% |
AS-SET
AS198291'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 14 are in fix.csv.
- Route object: none12
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 46.232.136.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.137.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.138.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.139.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.140.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.141.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.143.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 185.124.47.0/24 | No route object for it. A route object for 185.124.44.0/22 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 185.124.44.0/24 | No route object for it. A route object for 185.124.44.0/22 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 185.124.45.0/24 | No route object for it. A route object for 185.124.44.0/22 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 185.124.46.0/24 | No route object for it. A route object for 185.124.44.0/22 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
| Route object: none | 46.232.142.0/24 | No route object for it. A route object for 46.232.136.0/21 with origin AS198291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198291 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198291 whose prefix no peer sees AS198291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.232.136.0/21 | RIPE | Valid |
| 185.124.44.0/22 | 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.