bgpreport

Network · data from 2026-11-12

AS42584 TR-NGNCLOUD NGN Bilgi Teknolojileri Veri Merkezi ve Danismanlik Hizmetleri A.S.

Registry name: TR-NGNCLOUD NGN Bilgi Teknolojileri Veri Merkezi ve Danismanlik Hizmetleri A.S., TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42584, 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.
2a0a:b240::/32 No ROA RIR databaseRIPE 633 100% 68
2a0a:b240::/29 No ROA RIR databaseRIPE 632 99% 68
2a0a:b241::/32 No ROA RIR databaseRIPE 632 99% 68
2a0a:b242::/32 No ROA RIR databaseRIPE 632 99% 68
2a0a:b243::/32 No ROA RIR databaseRIPE 632 99% 68
2a0a:b244::/32 No ROA RIR databaseRIPE 632 99% 68
2a0a:b245::/32 No ROA RIR databaseRIPE 632 99% 68
2a0a:b246::/32 No ROA RIR databaseRIPE 632 99% 68
2a0a:b247::/32 No ROA RIR databaseRIPE 632 99% 68
185.200.28.0/24 Valid RIR databaseRIPE 673 100% 67
185.200.31.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none9
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:b240::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.633 of 636
ROA: none2a0a:b240::/29No ROA covers it. Add a ROA for AS42584, maxLength 29.632 of 636
ROA: none2a0a:b241::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636
ROA: none2a0a:b242::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636
ROA: none2a0a:b243::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636
ROA: none2a0a:b244::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636
ROA: none2a0a:b245::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636
ROA: none2a0a:b246::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636
ROA: none2a0a:b247::/32No ROA covers it. Add a ROA for AS42584, maxLength 32.632 of 636

Route objects not announced

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

185.200.28.0/22RIPENo ROA
185.200.29.0/24RIPENo ROA
185.200.30.0/24RIPENo ROA

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.