Network · data from 2026-11-12
AS48207 GLBBULUTTEKNOLOJISI-AS GLB Bulut Teknolojisi Limited Sirketi
Registry name: GLBBULUTTEKNOLOJISI-AS GLB Bulut Teknolojisi Limited Sirketi, TR · not in PeeringDB
48IPv4 routes
52.1% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
23No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS48207, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS48207, 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.
| 88.218.248.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.245.224.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.245.225.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.245.226.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 109.94.208.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.124.15.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.124.92.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.58.37.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.59.40.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.87.79.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.87.96.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.87.97.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.87.109.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.87.186.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.135.20.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.135.22.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.135.33.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.133.44.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.133.47.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.133.94.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.11.24.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.134.254.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.135.165.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 88.218.250.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 138.249.8.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 138.249.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 138.249.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 170.168.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 170.168.191.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.39.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 186.243.247.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 186.243.250.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 187.13.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 191.44.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.42.118.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.135.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.64.106.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.50.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.50.117.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.64.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.71.152.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.124.45.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.134.26.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 80.71.159.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 88.218.64.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 109.196.110.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 189.74.124.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 138.249.14.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS48207 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 24 are in fix.csv.
- ROA: none23
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 88.218.248.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 91.245.224.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 91.245.225.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 91.245.226.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 109.94.208.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 193.124.15.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 193.124.92.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.58.37.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.59.40.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.87.79.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.87.96.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.87.97.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.87.109.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.87.186.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.135.20.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.135.22.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 194.135.33.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 195.133.44.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 195.133.47.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 195.133.94.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 45.11.24.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 45.134.254.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
| ROA: none | 45.135.165.0/24 | No ROA covers it. Add a ROA for AS48207, maxLength 24. |
Route objects not announced
Route objects with origin AS48207 whose prefix no peer sees AS48207 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.88.90.0/24 | 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.