Network · data from 2026-11-12
AS208355 YAM Network
Registry name: yamnet YAM DIGITAL ALTYAPI VE VERI HIZMETLERI A.S., TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208355, 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.
| 95.133.139.0/24 | Valid | Other origin only | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS208355: RIPE::AS208355:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS208355 isn't in the set, or no route object for AS208355 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS208355 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS208355:AS-CUSTOMERS | RIPE | 124 | 15 | Yes | 1 |
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 1 are in fix.csv.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 95.133.139.0/24 | Route objects for it name AS6823. Add a route object with origin AS208355 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS208355 is announced.
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.