Network · data from 2026-11-12
AS47585 YIGITHOSTING
Registry name: YIGITHOSTING Yigit Hosting Bilisim E-Ticaret Gida Sanayi Ticaret Limited Sirketi, TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47585, 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.
| 62.76.230.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 78.135.111.0/24 | Valid | RIR databaseRIPE | 668 99% |
AS-SET
AS47585'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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 62.76.230.0/24 | ROAs covering it name AS198566, not AS47585; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS47585 should announce it, add a ROA for AS47585. |
| Route object: none | 62.76.230.0/24 | Route objects for it name AS198566. Add a route object with origin AS47585 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS47585 whose prefix no peer sees AS47585 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.136.7.0/24 | RIPE | Valid |
| 2a13:9500:a2::/48 | 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.