Incidents reported on status page for Firstoken https://status.firstoken.co/ https://d1lppblt9t2x15.cloudfront.net/logos/23a6ffb06a92b651cff836e49a41755b.png https://status.firstoken.co/ en https://status.firstoken.co/ Fri, 28 Nov 2025 17:15:17 +0000 https://status.firstoken.co/#cbbd15409ee9904956c8f3a6c5c0aeb61a657ad05384984c10910e052eaa7129 PATCH /proxy recovered https://status.firstoken.co/ Fri, 28 Nov 2025 17:14:57 +0000 https://status.firstoken.co/#8075cc328fe820a67522a53d8d6376a23f333904e06dccc67b86ab742b7c4a30 PUT /proxy recovered https://status.firstoken.co/ Fri, 28 Nov 2025 17:12:17 +0000 https://status.firstoken.co/#cbbd15409ee9904956c8f3a6c5c0aeb61a657ad05384984c10910e052eaa7129 PATCH /proxy went down https://status.firstoken.co/ Fri, 28 Nov 2025 17:06:16 +0000 https://status.firstoken.co/#fc1729e2e2edbb92b61c7b62b70c34dfde7aba6142c30f17fe319343f3714c3f PATCH /proxy recovered https://status.firstoken.co/ Fri, 28 Nov 2025 17:06:15 +0000 https://status.firstoken.co/#5cbb2dc69cf280f9470321b41b9e602a6fced9c0e3fa91410e1208d13a199b07 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Fri, 28 Nov 2025 17:03:17 +0000 https://status.firstoken.co/#fc1729e2e2edbb92b61c7b62b70c34dfde7aba6142c30f17fe319343f3714c3f PATCH /proxy went down https://status.firstoken.co/ Fri, 28 Nov 2025 17:02:54 +0000 https://status.firstoken.co/#8075cc328fe820a67522a53d8d6376a23f333904e06dccc67b86ab742b7c4a30 PUT /proxy went down https://status.firstoken.co/ Fri, 28 Nov 2025 16:58:14 +0000 https://status.firstoken.co/#5cbb2dc69cf280f9470321b41b9e602a6fced9c0e3fa91410e1208d13a199b07 POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:59:58 +0000 https://status.firstoken.co/#bb7654538a91a02341b40ed3fd7cd6f6d2a1baffd77f5c755a3c0c8e0eb6423a PATCH /proxy recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:48:01 +0000 https://status.firstoken.co/#8e8c1608b6f39987aad6fca77f88f4018b8058da476d54d6e9c565856e3e2937 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:47:38 +0000 https://status.firstoken.co/#5e0e4df67061ed169d9e536e192c00646c2b23e3d9dc9f8882758a852dac484b PUT /proxy recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:45:57 +0000 https://status.firstoken.co/#8e8c1608b6f39987aad6fca77f88f4018b8058da476d54d6e9c565856e3e2937 POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:42:37 +0000 https://status.firstoken.co/#6f68b7a033aaef5b5512f283d02c37912c5323eb2ca4521e2dfcd53f3f4a9bb0 GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:42:17 +0000 https://status.firstoken.co/#f9877a7f30acf35269ad41cd3cf3b0df663a4bd48b972330b0b4c07ffb421eb2 POST /proxy recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:41:59 +0000 https://status.firstoken.co/#50aed8f676d7b450d4ad5fde264dec208a03142cff963b7ddec84d0d4f1cb7fa POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:39:17 +0000 https://status.firstoken.co/#f9877a7f30acf35269ad41cd3cf3b0df663a4bd48b972330b0b4c07ffb421eb2 POST /proxy went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:38:57 +0000 https://status.firstoken.co/#bb7654538a91a02341b40ed3fd7cd6f6d2a1baffd77f5c755a3c0c8e0eb6423a PATCH /proxy went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:32:58 +0000 https://status.firstoken.co/#df712ed26e7d9bd83d6cbc1eb9dc6fc49a88459be175d9aa74523f986703145b PATCH /proxy recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:32:34 +0000 https://status.firstoken.co/#5e0e4df67061ed169d9e536e192c00646c2b23e3d9dc9f8882758a852dac484b PUT /proxy went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:30:56 +0000 https://status.firstoken.co/#50aed8f676d7b450d4ad5fde264dec208a03142cff963b7ddec84d0d4f1cb7fa POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:29:58 +0000 https://status.firstoken.co/#df712ed26e7d9bd83d6cbc1eb9dc6fc49a88459be175d9aa74523f986703145b PATCH /proxy went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:28:37 +0000 https://status.firstoken.co/#6f68b7a033aaef5b5512f283d02c37912c5323eb2ca4521e2dfcd53f3f4a9bb0 GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:21:37 +0000 https://status.firstoken.co/#7ddf8b0ad19dfc9182903be67c1b41661553bc4e3204405168fa684db3387c75 GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:20:59 +0000 https://status.firstoken.co/#0d06c9798e913b86cd6e9eb1e4039b3376413f4766b7113ab9cfaaf38409e8a1 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 13:16:01 +0000 https://status.firstoken.co/#7ddf8b0ad19dfc9182903be67c1b41661553bc4e3204405168fa684db3387c75 GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 13:06:36 +0000 https://status.firstoken.co/#cb28eec2d7eb6fd0efebdac121450b7d14b4393115a73a91ed6e0804ca0bc6a3 GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 12:39:09 +0000 https://status.firstoken.co/#290eee3136b83eec1fa2be640b765cccfa4322ea60bf1adb8465ac1c4d07f8cf POST /v1/detokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 12:27:56 +0000 https://status.firstoken.co/#0d06c9798e913b86cd6e9eb1e4039b3376413f4766b7113ab9cfaaf38409e8a1 POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 12:23:59 +0000 https://status.firstoken.co/#b9457bba2e97d512006e439ac3c5d28733363708ea57474a756f6035c9645a9f POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 12:18:13 +0000 https://status.firstoken.co/#290eee3136b83eec1fa2be640b765cccfa4322ea60bf1adb8465ac1c4d07f8cf POST /v1/detokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 12:10:02 +0000 https://status.firstoken.co/#cb28eec2d7eb6fd0efebdac121450b7d14b4393115a73a91ed6e0804ca0bc6a3 GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 12:03:41 +0000 https://status.firstoken.co/#abfebca956f704e5eea6497b0fdce01dd08c479ece4548b1ca4d00e128f207ca GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 11:52:34 +0000 https://status.firstoken.co/#abfebca956f704e5eea6497b0fdce01dd08c479ece4548b1ca4d00e128f207ca GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 11:51:55 +0000 https://status.firstoken.co/#b9457bba2e97d512006e439ac3c5d28733363708ea57474a756f6035c9645a9f POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 11:48:38 +0000 https://status.firstoken.co/#423ec34fe0283c7304d486a31e279336d2d14806fc086a85260eb08d9b9ae236 GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 11:47:58 +0000 https://status.firstoken.co/#6a7ae33d59c1e4a659a1634c9fed1fabde3392d2a1451d94c107bfcc9bc1cc8c POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 11:45:08 +0000 https://status.firstoken.co/#df491fe08e5e5747ba243df171e033ff930775229faa5acc124b07dca832b128 POST /v1/detokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 11:42:44 +0000 https://status.firstoken.co/#df491fe08e5e5747ba243df171e033ff930775229faa5acc124b07dca832b128 POST /v1/detokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 11:37:32 +0000 https://status.firstoken.co/#423ec34fe0283c7304d486a31e279336d2d14806fc086a85260eb08d9b9ae236 GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 11:36:56 +0000 https://status.firstoken.co/#6a7ae33d59c1e4a659a1634c9fed1fabde3392d2a1451d94c107bfcc9bc1cc8c POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 11:30:38 +0000 https://status.firstoken.co/#5b0ec69a8fd41089dfbcda46ee4097ea500760a53deb5baeace7b497e2a1b37e GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 11:29:58 +0000 https://status.firstoken.co/#a0fa2436f0b420bf0d4d54aa749980aa3846d7b414893ad759e5a2bc093d6844 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 11:18:56 +0000 https://status.firstoken.co/#a0fa2436f0b420bf0d4d54aa749980aa3846d7b414893ad759e5a2bc093d6844 POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 11:16:32 +0000 https://status.firstoken.co/#5b0ec69a8fd41089dfbcda46ee4097ea500760a53deb5baeace7b497e2a1b37e GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 05:08:47 +0000 https://status.firstoken.co/#687d36173e42c77c75323cff87041bc90d022603a97be78b2b02d78f0184ebaa POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 05:00:45 +0000 https://status.firstoken.co/#687d36173e42c77c75323cff87041bc90d022603a97be78b2b02d78f0184ebaa POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 04:45:25 +0000 https://status.firstoken.co/#4ba293284d9f3f76d12144b13e4783c994ce1766f7fc383944bed17a8143b028 GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 04:41:46 +0000 https://status.firstoken.co/#4204e01a8e2eccfe6d1e4bca3ec1320330188afac82583b1395592a60818dc88 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 04:39:50 +0000 https://status.firstoken.co/#4ba293284d9f3f76d12144b13e4783c994ce1766f7fc383944bed17a8143b028 GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Sat, 22 Nov 2025 04:30:46 +0000 https://status.firstoken.co/#4204e01a8e2eccfe6d1e4bca3ec1320330188afac82583b1395592a60818dc88 POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 04:15:26 +0000 https://status.firstoken.co/#8957cb272a49f2d68444353dc6e1d30f9a4c45a28afd16e9a4c05d0d869e1dff GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Sat, 22 Nov 2025 04:15:07 +0000 https://status.firstoken.co/#4e9148dcb60cda9ecf6683414d520b6557c3a46b040f6c3beea2bd3510e0ed34 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sat, 22 Nov 2025 04:06:43 +0000 https://status.firstoken.co/#4e9148dcb60cda9ecf6683414d520b6557c3a46b040f6c3beea2bd3510e0ed34 POST /v1/tokenization/simple went down https://status.firstoken.co/ Sat, 22 Nov 2025 04:04:21 +0000 https://status.firstoken.co/#8957cb272a49f2d68444353dc6e1d30f9a4c45a28afd16e9a4c05d0d869e1dff GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Mon, 20 Oct 2025 18:01:46 +0000 https://status.firstoken.co/#fa6877b7633455f5fe73cd00be9d7cf930eeca6f6e420fff0e89694f276b6648 console.firstoken.co/login recovered https://status.firstoken.co/ Mon, 20 Oct 2025 17:55:00 +0000 https://status.firstoken.co/#fa6877b7633455f5fe73cd00be9d7cf930eeca6f6e420fff0e89694f276b6648 console.firstoken.co/login went down https://status.firstoken.co/ Mon, 20 Oct 2025 17:35:29 +0000 https://status.firstoken.co/#e67bf5d98ae9cd232903ae3751b1c09e3f1b371ce748c9463b3466530654702d console.firstoken.co/login recovered https://status.firstoken.co/ Mon, 20 Oct 2025 17:30:46 +0000 https://status.firstoken.co/#e67bf5d98ae9cd232903ae3751b1c09e3f1b371ce748c9463b3466530654702d console.firstoken.co/login went down https://status.firstoken.co/ Mon, 20 Oct 2025 17:25:40 +0000 https://status.firstoken.co/#2974c6f9b04edb28773fbba2b0c066f7adfc63134e1595ac33e9bd704162010b www.firstoken.co recovered https://status.firstoken.co/ Mon, 20 Oct 2025 17:19:35 +0000 https://status.firstoken.co/#2974c6f9b04edb28773fbba2b0c066f7adfc63134e1595ac33e9bd704162010b www.firstoken.co went down https://status.firstoken.co/ Mon, 20 Oct 2025 16:59:44 +0000 https://status.firstoken.co/#dff85330730586053d0a13f31d9bbb6c195ebfed689ad81a7a813fbf4792612c GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Mon, 20 Oct 2025 16:55:13 +0000 https://status.firstoken.co/#6f88c53ff4f79ef2b4f667d242c6990e7d0822d4fdf15671c2f5d11d6fe8db65 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Mon, 20 Oct 2025 16:55:11 +0000 https://status.firstoken.co/#a9af53f2a6a766767aa1780666663f9228f810240a227fef117a1ca09298f8d6 POST /v1/detokenization/simple recovered https://status.firstoken.co/ Mon, 20 Oct 2025 15:01:28 +0000 https://status.firstoken.co/#6f88c53ff4f79ef2b4f667d242c6990e7d0822d4fdf15671c2f5d11d6fe8db65 POST /v1/tokenization/simple went down https://status.firstoken.co/ Mon, 20 Oct 2025 15:00:58 +0000 https://status.firstoken.co/#a9af53f2a6a766767aa1780666663f9228f810240a227fef117a1ca09298f8d6 POST /v1/detokenization/simple went down https://status.firstoken.co/ Mon, 20 Oct 2025 14:57:37 +0000 https://status.firstoken.co/#dff85330730586053d0a13f31d9bbb6c195ebfed689ad81a7a813fbf4792612c GET /v1/tokens/:id/inspect went down https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/incident/747244 Mon, 20 Oct 2025 11:41:00 -0000 https://status.firstoken.co/incident/747244#af986cac3fd80fd62e5e7bfc99d02d14b4939a88825037bdd299ff2bced9e4a3 At approximately 07:11 UTC, Firstoken began experiencing intermittent errors and increased latency in some services hosted in the AWS N. Virginia (us-east-1) region. According to the AWS Service Health Dashboard, multiple AWS services —including EC2, Lambda, and DynamoDB— reported increased error rates and latencies due to an underlying DNS resolution issue. This incident temporarily affected the availability of certain backend operations and caused delays in API responses for a subset of customers. AWS engineers have applied mitigations, and recovery efforts are ongoing. Firstoken’s core systems remain stable, and we continue to monitor the situation closely. Further updates will be provided as AWS releases new information. Timeline (UTC) • 07:11 UTC – AWS reports increased error rates and latencies across multiple services in us-east-1. • 08:26 UTC – AWS confirms significant error rates for DynamoDB and other services. • 09:01 UTC – AWS identifies the root cause as a DNS resolution issue affecting DynamoDB and dependent services. • 09:22 UTC – AWS applies initial mitigations; early signs of recovery observed. • 10:35 UTC – AWS confirms the DNS issue is fully mitigated; most services recovered. • 11:08 UTC – Ongoing work to resolve EC2 launch errors and Lambda event processing delays. Impact • Temporary API latency and degraded performance in selected tokenization and proxy operations. Status Monitoring – Partial Recovery https://status.firstoken.co/ Mon, 20 Oct 2025 09:25:58 +0000 https://status.firstoken.co/#fad778762a9c89697110c3992a4ced7df0f9e2349989b951ece1ea0a7213f5dc PATCH /proxy recovered https://status.firstoken.co/ Mon, 20 Oct 2025 09:25:58 +0000 https://status.firstoken.co/#bb97141ad33e915b11edfbdd3914c370cd22d7da0309c28605bacab6a56d566d POST /v1/tokenization/simple recovered https://status.firstoken.co/ Mon, 20 Oct 2025 09:25:47 +0000 https://status.firstoken.co/#cc0de680e1f0cd351fee626ee49453d46a5ccc104fa43bbf2d09f48a623d7c1f POST /v1/detokenization/simple recovered https://status.firstoken.co/ Mon, 20 Oct 2025 09:25:40 +0000 https://status.firstoken.co/#28d0fb0edd3490bf05e03b5e4e2b7149ebc085670fb160404aceaf1bd79c6306 PUT /proxy recovered https://status.firstoken.co/ Mon, 20 Oct 2025 09:23:42 +0000 https://status.firstoken.co/#ed131d624511fc1f7e2713847091a50717e1565484754e59994319e7698c7a25 GET /v1/tokens/:id/inspect recovered https://status.firstoken.co/ Mon, 20 Oct 2025 09:23:32 +0000 https://status.firstoken.co/#4e1e1adbc60b8c9012fde634fb53481ec1057d1e482fd4ac2541429bf9a3e5dd POST /proxy recovered https://status.firstoken.co/ Mon, 20 Oct 2025 09:23:12 +0000 https://status.firstoken.co/#d9a75a6e931d0b150d36d3d2bc78d212ba3a0e7a7dc8feff42ae813416ceec55 POST /routes/:id recovered https://status.firstoken.co/ Mon, 20 Oct 2025 06:52:48 +0000 https://status.firstoken.co/#4e1e1adbc60b8c9012fde634fb53481ec1057d1e482fd4ac2541429bf9a3e5dd POST /proxy went down https://status.firstoken.co/ Mon, 20 Oct 2025 06:52:42 +0000 https://status.firstoken.co/#d9a75a6e931d0b150d36d3d2bc78d212ba3a0e7a7dc8feff42ae813416ceec55 POST /routes/:id went down https://status.firstoken.co/ Mon, 20 Oct 2025 06:52:37 +0000 https://status.firstoken.co/#bb97141ad33e915b11edfbdd3914c370cd22d7da0309c28605bacab6a56d566d POST /v1/tokenization/simple went down https://status.firstoken.co/ Mon, 20 Oct 2025 06:52:36 +0000 https://status.firstoken.co/#fad778762a9c89697110c3992a4ced7df0f9e2349989b951ece1ea0a7213f5dc PATCH /proxy went down https://status.firstoken.co/ Mon, 20 Oct 2025 06:52:10 +0000 https://status.firstoken.co/#28d0fb0edd3490bf05e03b5e4e2b7149ebc085670fb160404aceaf1bd79c6306 PUT /proxy went down https://status.firstoken.co/ Mon, 20 Oct 2025 06:50:16 +0000 https://status.firstoken.co/#ed131d624511fc1f7e2713847091a50717e1565484754e59994319e7698c7a25 GET /v1/tokens/:id/inspect went down https://status.firstoken.co/ Mon, 20 Oct 2025 06:49:17 +0000 https://status.firstoken.co/#cc0de680e1f0cd351fee626ee49453d46a5ccc104fa43bbf2d09f48a623d7c1f POST /v1/detokenization/simple went down https://status.firstoken.co/ Sun, 12 Oct 2025 09:04:48 +0000 https://status.firstoken.co/#c7e2cad91485877cb15e10392f89570eb6c8acf8c0b96aefc4e94a73efc85b7f POST /routes/:id recovered https://status.firstoken.co/ Sun, 12 Oct 2025 09:01:54 +0000 https://status.firstoken.co/#c7e2cad91485877cb15e10392f89570eb6c8acf8c0b96aefc4e94a73efc85b7f POST /routes/:id went down https://status.firstoken.co/ Sun, 28 Sep 2025 04:25:36 +0000 https://status.firstoken.co/#fdd002d0ccdbd6434813508b94e33f194b62e0530202cc414a81320e9ade9b21 POST /v1/tokenization/simple recovered https://status.firstoken.co/ Sun, 28 Sep 2025 04:20:35 +0000 https://status.firstoken.co/#fdd002d0ccdbd6434813508b94e33f194b62e0530202cc414a81320e9ade9b21 POST /v1/tokenization/simple went down https://status.firstoken.co/ Mon, 22 Sep 2025 21:46:25 +0000 https://status.firstoken.co/#f6fe9e1803ba23f552aac6a6a6ac0297b8ee8a385b5e2ba5e42934892c6f80fe console.firstoken.co/login recovered https://status.firstoken.co/ Mon, 22 Sep 2025 21:37:37 +0000 https://status.firstoken.co/#f6fe9e1803ba23f552aac6a6a6ac0297b8ee8a385b5e2ba5e42934892c6f80fe console.firstoken.co/login went down