bgpreport

Network · data from 2026-11-12

AS202973 RMDY-AS Remedy Bilisim Teknolojileri A.S.

Registry name: RMDY-AS Remedy Bilisim Teknolojileri A.S., TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202973, 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.
104.247.180.0/24 Valid Other origin only 673 100% 67
185.73.129.0/24 Valid Other origin only 673 100% 67
194.62.54.0/24 Valid RIR databaseRIPE 673 100% 67
193.30.113.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none104.247.180.0/24Route objects for it name AS57152. Add a route object with origin AS202973 in the RIR database for the space.673 of 673
Route object: none185.73.129.0/24Route objects for it name AS57152. Add a route object with origin AS202973 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS202973 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.