Incidents reported on status page for RSR Development https://status.rsrdev.com/ https://d1lppblt9t2x15.cloudfront.net/logos/40d7599fcd760997ed24308c3b893fc9.png https://status.rsrdev.com/ en https://status.rsrdev.com/ Tue, 02 Jun 2026 02:55:51 +0000 https://status.rsrdev.com/#f28d879e02dc17b72b681a19b56dc8dab3b1af75744bfe1460ae1d5e9b5ec509 Ops Network recovered https://status.rsrdev.com/incident/910568 Tue, 02 Jun 2026 02:44:00 -0000 https://status.rsrdev.com/incident/910568#255970d243d8282a202d5d313bed197ce5f2b5fbb90848ecc180850bea732926 ## Resolved The mitigation has been successfully deployed across the Ops Network, and this incident has now been fully resolved. Our monitoring indicates that legitimate API requests are being processed normally and are no longer being incorrectly classified as spam traffic. We have completed our review of the affected traffic and have reached out directly to impacted clients with relevant information regarding requests that were incorrectly blocked during the incident window. Following deployment, we conducted additional validation and security testing, including simulated distributed denial-of-service (DDoS) and other illegitimate traffic scenarios. These tests confirmed that malicious and unauthorized requests continue to be correctly identified and blocked, while legitimate traffic is processed as expected. We apologize for the inconvenience caused by this issue and appreciate our clients' patience while our team investigated, mitigated, and resolved the problem. We will continue to review our traffic classification systems and operational processes to help prevent similar incidents in the future. https://status.rsrdev.com/ Tue, 02 Jun 2026 02:43:16 +0000 https://status.rsrdev.com/#f28d879e02dc17b72b681a19b56dc8dab3b1af75744bfe1460ae1d5e9b5ec509 Ops Network went down https://status.rsrdev.com/ Tue, 02 Jun 2026 02:40:41 +0000 https://status.rsrdev.com/#0443931ba510f1cf728b459c95d518f249624747ec5bb8be5fb6c7c26da2ec22 Ops Network recovered https://status.rsrdev.com/incident/910568 Sun, 31 May 2026 00:28:00 -0000 https://status.rsrdev.com/incident/910568#9ab356bc9d2cdd2a7fdd156baa0a8c2b0756158128adc585468bdd30303ce502 ## Mitigation Deployed We have successfully implemented a mitigation for the traffic classification issue affecting a subset of API requests within the Ops Network and have begun rolling it out across the network. The mitigation is designed to prevent legitimate API traffic from being incorrectly identified as spam traffic, reducing the likelihood of unintended blocking, filtering, or rate-limiting behavior. Deployment is proceeding in phases to ensure stability and allow for continuous monitoring throughout the rollout process. The majority of premium and white-label clients remain unaffected, and client-managed instances and servers within the Ops Network continue to operate normally. We are closely monitoring the effectiveness of the mitigation and will provide further updates as deployment progresses. https://status.rsrdev.com/incident/898123 Fri, 29 May 2026 14:17:00 -0000 https://status.rsrdev.com/incident/898123#6934a44eb1953caa85ac1b8a20bafddd232978b4e80947bb48e94897dca24e78 Hardware updates were completed, and no service disruption was present. https://status.rsrdev.com/incident/910568 Thu, 28 May 2026 04:39:00 -0000 https://status.rsrdev.com/incident/910568#73a13d341e0f85cf55f9f272b90478ae2c8a6dab1e4177ffa56d57cf36bd8bd3 ## Identified Our investigation has identified the source of the issue affecting a subset of API requests within the Ops Network. Under specific conditions, legitimate API traffic was incorrectly classified as spam traffic, resulting in unintended blocking, filtering, or rate-limiting of affected requests. We have confirmed the root cause and are actively deploying mitigations to reduce impact while we work toward a permanent resolution. The majority of premium and white-label clients remain unaffected. Client-managed instances and servers operating within the Ops Network are not impacted by this issue. We will continue to provide updates as mitigation efforts progress and additional improvements are rolled out. https://status.rsrdev.com/incident/910568 Wed, 27 May 2026 02:41:00 -0000 https://status.rsrdev.com/incident/910568#35fef1045259a09957b168b2006b7888c2e7f16c60da6186ced1937262e0ff8c ## Investigating We are currently investigating an issue within the Ops Network that may be causing a small subset of legitimate API requests to be incorrectly classified as spam traffic. Affected requests may experience unexpected blocking, filtering, or rate-limiting behavior. Our engineering team is actively analyzing network traffic and system logs to determine the root cause and scope of the issue. This incident **does not** affect the majority of premium or white-label clients, and no client-managed instances or servers within the Ops Network are impacted at this time. We will provide additional updates as more information becomes available. https://status.rsrdev.com/ Tue, 26 May 2026 14:40:15 +0000 https://status.rsrdev.com/#0443931ba510f1cf728b459c95d518f249624747ec5bb8be5fb6c7c26da2ec22 Ops Network went down https://status.rsrdev.com/ Tue, 26 May 2026 14:37:09 +0000 https://status.rsrdev.com/#305b536b42aef04a9743bbe3a82987b52911f3d50ec8750202f0437d1586a930 Ops Network recovered https://status.rsrdev.com/ Tue, 26 May 2026 14:10:18 +0000 https://status.rsrdev.com/#305b536b42aef04a9743bbe3a82987b52911f3d50ec8750202f0437d1586a930 Ops Network went down https://status.rsrdev.com/ Mon, 25 May 2026 05:34:19 +0000 https://status.rsrdev.com/#ff98ca69b5c359741560befd18972e2a14146fe98e877008f859ddf1f46d7f94 Ops Network recovered https://status.rsrdev.com/ Mon, 25 May 2026 05:32:05 +0000 https://status.rsrdev.com/#ff98ca69b5c359741560befd18972e2a14146fe98e877008f859ddf1f46d7f94 Ops Network went down https://status.rsrdev.com/incident/898123 Sun, 17 May 2026 19:23:00 -0000 https://status.rsrdev.com/incident/898123#c70e0165c4c7aed6cbf7f5fb5803b18d6612852ace9f350259b5e7eb5dca776d We’re upgrading our hardware infrastructure to deliver a more reliable and higher-performance service for all users. During this process, some servers may experience temporary performance degradation. https://status.rsrdev.com/ Fri, 15 May 2026 02:13:34 +0000 https://status.rsrdev.com/#a05cfd9b72b7ff927b293c2d4749b6a38457b999e057562922349d62df28427b Ops Network recovered https://status.rsrdev.com/ Fri, 15 May 2026 02:11:17 +0000 https://status.rsrdev.com/#a05cfd9b72b7ff927b293c2d4749b6a38457b999e057562922349d62df28427b Ops Network went down https://status.rsrdev.com/ Mon, 11 May 2026 08:25:13 +0000 https://status.rsrdev.com/#f7cf56faabdb1c531c4b3fd8d0665ba18db1747edcf01a9d1177c09db4aff115 Ops Network recovered https://status.rsrdev.com/ Mon, 11 May 2026 04:52:42 +0000 https://status.rsrdev.com/#f7cf56faabdb1c531c4b3fd8d0665ba18db1747edcf01a9d1177c09db4aff115 Ops Network went down https://status.rsrdev.com/ Mon, 11 May 2026 04:49:13 +0000 https://status.rsrdev.com/#d5a23117c524fa24be8f9d7683578cf60c19a995378fe04b55147cec41c324c8 Ops Network recovered https://status.rsrdev.com/ Mon, 11 May 2026 04:19:16 +0000 https://status.rsrdev.com/#d5a23117c524fa24be8f9d7683578cf60c19a995378fe04b55147cec41c324c8 Ops Network went down https://status.rsrdev.com/ Wed, 06 May 2026 04:22:19 +0000 https://status.rsrdev.com/#1686e26e005c74fa1320ec11f66653cf6e2672cfe0466b8e9c2f1a3fcbdb8f0a Ops Network recovered https://status.rsrdev.com/ Wed, 06 May 2026 04:02:09 +0000 https://status.rsrdev.com/#1686e26e005c74fa1320ec11f66653cf6e2672cfe0466b8e9c2f1a3fcbdb8f0a Ops Network went down https://status.rsrdev.com/ Wed, 06 May 2026 00:40:30 +0000 https://status.rsrdev.com/#c7e24d4d0d00dbae4bc799d815e514076a30ebc1130a569b94a3e82bae2a1146 Ops Network recovered https://status.rsrdev.com/ Wed, 06 May 2026 00:37:10 +0000 https://status.rsrdev.com/#c7e24d4d0d00dbae4bc799d815e514076a30ebc1130a569b94a3e82bae2a1146 Ops Network went down https://status.rsrdev.com/ Sun, 03 May 2026 17:43:20 +0000 https://status.rsrdev.com/#73f2514129c2e5cebbe9a6bc099be8c0dddeff18ffe1f17a34400293d44b7412 Ops Network recovered https://status.rsrdev.com/ Sun, 03 May 2026 12:29:09 +0000 https://status.rsrdev.com/#73f2514129c2e5cebbe9a6bc099be8c0dddeff18ffe1f17a34400293d44b7412 Ops Network went down https://status.rsrdev.com/ Thu, 30 Apr 2026 18:46:57 +0000 https://status.rsrdev.com/#227c3fc4e21eb4159ed67c3ffa8ca65e9a577f55ee324971215a8aeab024cf0f Ops Network recovered https://status.rsrdev.com/ Thu, 30 Apr 2026 18:31:08 +0000 https://status.rsrdev.com/#227c3fc4e21eb4159ed67c3ffa8ca65e9a577f55ee324971215a8aeab024cf0f Ops Network went down https://status.rsrdev.com/ Thu, 30 Apr 2026 14:25:11 +0000 https://status.rsrdev.com/#1b9389bf8ef9307aabf2079ab5ded60c0a13d8f2d23142c564d6a74ad46b75ad Ops Network recovered https://status.rsrdev.com/ Thu, 30 Apr 2026 12:23:09 +0000 https://status.rsrdev.com/#1b9389bf8ef9307aabf2079ab5ded60c0a13d8f2d23142c564d6a74ad46b75ad Ops Network went down https://status.rsrdev.com/ Thu, 30 Apr 2026 11:22:26 +0000 https://status.rsrdev.com/#1abef7021b9c840b7d5c1bde475143939d41276aba65edd59b4ed00561e7266d Ops Network recovered https://status.rsrdev.com/ Thu, 30 Apr 2026 11:05:09 +0000 https://status.rsrdev.com/#1abef7021b9c840b7d5c1bde475143939d41276aba65edd59b4ed00561e7266d Ops Network went down https://status.rsrdev.com/ Thu, 30 Apr 2026 10:58:17 +0000 https://status.rsrdev.com/#6771f5b9ff3a9b7c08f832cde21da239d1c47716eacc50d0c52c002f2f2e868f Ops Network recovered https://status.rsrdev.com/ Thu, 30 Apr 2026 09:43:29 +0000 https://status.rsrdev.com/#6771f5b9ff3a9b7c08f832cde21da239d1c47716eacc50d0c52c002f2f2e868f Ops Network went down