bgpreport

Network · data from 2026-11-12

AS214466 Olfe Cloud

Registry name: Olfe AE Olfe Teknoloji ve Ticaret Limited Sirketi, TR · PeeringDB

3IPv4 routes 0.0% RPKI valid · 0.0% with a route object
18IPv6 routes 100.0% RPKI valid · 11.1% with a route object
3RPKI invalid 3 origin · 0 maxLength
0No ROA 19 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS214466, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214466, 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.

45.139.198.0/24 Invalid: origin None 107 16% 38
45.139.199.0/24 Invalid: origin None 41 6%low visibility 24
95.214.174.0/24 Invalid: origin None 1 0%low visibility 1
2a14:9400:2000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:3000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:4000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:5000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:6000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:7000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:8000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:9000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:a000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:b000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:c000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:d000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:e000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9400:f000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9401::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9401:1000::/36 Valid Nonecovered by 2a14:9400::/29 631 99% 67
2a14:9401:3000::/36 Valid RIR databaseRIPE 632 99% 67
2a14:9401:5000::/36 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS214466: AS214466:AS-OLFE-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 (AS214466 isn't in the set, or no route object for AS214466 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.

NameDatabaseASNsSets Route objectsAS214466 in itNot covered
AS214466:AS-OLFE-CUSTOMERS RIPE 235788 Yes 3

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 26 are in fix.csv.

  • ROA: origin3
  • Route object: none19
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin45.139.198.0/24ROAs covering it name AS401107, not AS214466. If AS214466 should announce it, add a ROA for AS214466.107 of 673
Route object: none45.139.198.0/24No route object for it. Add a route object with origin AS214466 in the RIR database for the space.107 of 673
ROA: origin45.139.199.0/24ROAs covering it name AS401107, not AS214466. If AS214466 should announce it, add a ROA for AS214466.41 of 673
Route object: none45.139.199.0/24No route object for it. Add a route object with origin AS214466 in the RIR database for the space.41 of 673
ROA: origin95.214.174.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214466 should announce it, add a ROA for AS214466.1 of 673
Route object: none95.214.174.0/24No route object for it. Add a route object with origin AS214466 in the RIR database for the space.1 of 673
Route object: none2a14:9400:2000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:3000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:4000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:5000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:6000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:7000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:8000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:9000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:a000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:b000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:c000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:d000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:e000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9400:f000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9401::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636
Route object: none2a14:9401:1000::/36No route object for it. A route object for 2a14:9400::/29 with origin AS214466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214466 in the RIR database for the space.631 of 636

Route objects not announced

Route objects with origin AS214466 whose prefix no peer sees AS214466 announce. Many are kept on purpose (backup routes, space announced only in some places).

2.56.248.0/24RIPEInvalid: origin
213.218.251.0/24RADB, RIPEValid
2a14:9400::/29RIPEValid
2a14:9400:1337::/48RIPEValid

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.