Network · data from 2026-11-12
AS198436 GOLDSURF GOLDSURF INTERNET LTD
Registry name: GOLDSURF GOLDSURF INTERNET LTD, TR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198436, 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.
| 37.72.48.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.49.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.50.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.51.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.52.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.53.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.54.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.55.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.56.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.57.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.58.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.59.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.60.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.61.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.62.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
| 37.72.63.0/24 | Valid | Nonecovered by 37.72.48.0/20 | 673 100% |
AS-SET
AS198436 isn't in PeeringDB, where networks name their 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: none16
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 37.72.48.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.49.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.50.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.51.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.52.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.53.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.54.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.55.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.56.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.57.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.58.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.59.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.60.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.61.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.62.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
| Route object: none | 37.72.63.0/24 | No route object for it. A route object for 37.72.48.0/20 with origin AS198436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198436 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198436 whose prefix no peer sees AS198436 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.72.48.0/20 | 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.