bgpreport

Network · data from 2026-11-12

AS208594 Netbone Telekomunikasyon AS208594

Registry name: NETBONE Netbone Telekomunikasyon A.S., TR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS208594, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS208594, 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.94.150.0/24 Valid Other origin onlycovered by 45.94.148.0/22 671 100% 66
45.94.148.0/24 Valid RIR databaseRIPE 671 100% 66
45.94.151.0/24 Valid RIR databaseRIPE 671 100% 66
2a0e:2ec0:3::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS208594'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 10 are in fix.csv.

  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none45.94.150.0/24Route objects for it name AS48814. A route object for 45.94.148.0/22 with origin AS208594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208594 in the RIR database for the space.671 of 673

Route objects not announced

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

45.94.148.0/22RIPEValid
45.94.149.0/24RIPEValid
154.52.101.0/24RADBNo ROA
154.52.114.0/24RADBNo ROA
2a0e:2ec0::/29RIPEValid
2a0e:2ec0:1::/48RIPEValid
2a0e:2ec0:2::/48RIPEValid
2a0e:2ec0:4::/48RIPEValid
2a0e:2ec0:5::/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.