bgpreport

Network · data from 2026-11-12

AS48737 DoraTelekom Dorabase Veri Merkezi Hizmetleri A.S.

Registry name: DoraTelekom Dorabase Veri Merkezi Hizmetleri A.S., TR · not in PeeringDB

48IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 0.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
5Route objects not announced registered with origin AS48737, seen from no peer

Announced routes

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

2a02:dc40::/48 Valid None 634 100% 67
95.128.56.0/24 Valid RIR databaseRIPE 672 100% 66
95.128.57.0/24 Valid RIR databaseRIPE 672 100% 66
95.128.58.0/24 Valid RIR databaseRIPE 672 100% 66
95.128.60.0/24 Valid RIR databaseRIPE 672 100% 66
95.128.61.0/24 Valid RIR databaseRIPE 672 100% 66
95.128.62.0/24 Valid RIR databaseRIPE 672 100% 66
95.128.63.0/24 Valid RIR databaseRIPE 672 100% 66
185.56.237.0/24 Valid RIR databaseRIPE 672 100% 66
185.56.238.0/24 Valid RIR databaseRIPE 672 100% 66
185.59.72.0/24 Valid RIR databaseRIPE 672 100% 66
185.59.73.0/24 Valid RIR databaseRIPE 672 100% 66
185.59.74.0/24 Valid RIR databaseRIPE 672 100% 66
185.59.75.0/24 Valid RIR databaseRIPE 672 100% 66
193.42.100.0/24 Valid RIR databaseRIPE 672 100% 66
37.58.17.0/24 Valid RIR databaseRIPE 671 100% 66
37.58.20.0/24 Valid RIR databaseRIPE 671 100% 66
37.58.23.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.144.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.145.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.146.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.147.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.148.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.149.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.150.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.151.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.152.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.154.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.155.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.156.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.157.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.158.0/24 Valid RIR databaseRIPE 671 100% 66
46.20.159.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.96.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.97.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.98.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.99.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.100.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.101.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.102.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.103.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.104.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.105.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.106.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.107.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.108.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.109.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.110.0/24 Valid RIR databaseRIPE 671 100% 66
81.22.111.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

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

  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none2a02:dc40::/48No route object for it. Add a route object with origin AS48737 in the RIR database for the space.634 of 636

Route objects not announced

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

31.169.75.0/24RIPEValid
37.58.19.0/24RIPEValid
46.20.153.0/24RIPEValid
185.56.239.0/24RIPEValid
195.49.238.0/24RIPEValid

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.