Network · data from 2026-11-12
AS35356 GO p.l.c., go mobile (Malta)
Registry name: MT-GOMOBILE-AS GO p.l.c., MT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35356, 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.
| 83.142.248.0/22 | Valid | None | 673 100% |
| 83.142.255.0/24 | Valid | None | 673 100% |
| 80.93.149.0/24 | Valid | Nonecovered by 80.93.144.0/21 | 672 100% |
| 80.93.146.0/24 | Valid | Nonecovered by 80.93.144.0/21 | 671 100% |
| 80.93.147.0/24 | Valid | Nonecovered by 80.93.144.0/21 | 671 100% |
| 80.93.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 80.93.156.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.93.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS35356'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 17 are in fix.csv.
- Route object: none5
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 83.142.248.0/22 | No route object for it. Add a route object with origin AS35356 in the RIR database for the space. |
| Route object: none | 83.142.255.0/24 | No route object for it. Add a route object with origin AS35356 in the RIR database for the space. |
| Route object: none | 80.93.149.0/24 | No route object for it. A route object for 80.93.144.0/21 with origin AS35356 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35356 in the RIR database for the space. |
| Route object: none | 80.93.146.0/24 | No route object for it. A route object for 80.93.144.0/21 with origin AS35356 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35356 in the RIR database for the space. |
| Route object: none | 80.93.147.0/24 | No route object for it. A route object for 80.93.144.0/21 with origin AS35356 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35356 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS35356 whose prefix no peer sees AS35356 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.93.144.0/21 | RIPE | Valid |
| 80.93.152.0/22 | RIPE | Invalid: maxLength |
| 80.93.154.0/24 | RIPE | Valid |
| 80.93.155.0/24 | RIPE | Valid |
| 80.93.156.0/22 | RIPE | Invalid: maxLength |
| 80.93.158.0/24 | RIPE | Invalid: maxLength |
| 80.93.159.0/24 | RIPE | Valid |
| 83.142.249.0/24 | RIPE | Invalid: maxLength |
| 83.142.250.0/24 | RIPE | Invalid: maxLength |
| 2a01:a0::/32 | RIPE | No ROA |
| 2a01:a0:1::/48 | RIPE | No ROA |
| 2a01:a0:6969::/48 | 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.