A watchlist update has been rolled back. Holds are being released.
An increased rate of valid travelers are being held at the entry boundary due to watchlist false positives.
A watchlist update has been rolled back. Holds are being released.
An increased rate of valid travelers are being held at the entry boundary due to watchlist false positives.
All incorrect charges have been refunded. No further action is required.
Affected accounts have been identified. Refunds are being issued.
A small number of accounts have been charged temporal handling fees on provisional credit drawdowns that should be exempt.
Voucher validation is operating within nominal latency.
The validation cache has been flushed. Latency is decreasing.
Voucher code validation is timing out for a subset of requests.
All SWIFT-T transfers are succeeding. The gateway has confirmed restoration.
The gateway is undergoing maintenance in the originating timeline. We are routing around it.
A correspondent-bank gateway is intermittently returning 503 errors on SWIFT-T transfers.
All handoffs into ord-central-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into ord-central-1 are failing. Active travelers in ord-central-1 are unaffected, but new operator-assisted operations cannot complete.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
Egress is operating normally in nrt-asia-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in nrt-asia-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
Latency in lhr-europe-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in lhr-europe-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in lhr-europe-1. Median latency is unaffected. No impact to ongoing traversals.
Scales have been recalibrated. Mass-limit checks are operating correctly.
A calibration error in the boundary scale has been identified. Affected portals are being held.
Some travelers in syd-pacific-1 are being rejected at the entry boundary on mass-limit checks. Affected weight range: 65–80 kg.
Dispatch to lhr-europe-1 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to lhr-europe-1 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into lhr-europe-1 are failing to complete. Stuck-in-portal events in this region are being queued.
Queue depth has returned to nominal. Dispatch SLAs are being met.
Additional operators have been brought online in ord-central-1. The queue is draining.
Recovery dispatch queue depth has exceeded nominal thresholds. P3 and P4 dispatches may experience elevated wait times.
Latency in syd-pacific-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in syd-pacific-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in syd-pacific-1. Median latency is unaffected. No impact to ongoing traversals.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Custody-held travelers from this event will be reconciled at the close of the current billing cycle. Affected accounts will receive a notice from their operator.
Duplicate rate has returned to nominal. No additional travelers have been placed in custody.
The duplicate rate has been traced to a stuck inter-timeline reconciliation worker. We are restarting the worker.
We are seeing an elevated rate of duplicate emergence events. Affected travelers are being placed in custody hold per protocol.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Reconciliation has completed. No travelers were released from custody as a result of this delay.
Scheduled custody hold reconciliation is running behind. Holds will continue to be honored.
Dispatch to iad-east-1 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to iad-east-1 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into iad-east-1 are failing to complete. Stuck-in-portal events in this region are being queued.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Recalibration complete. All portals in ord-central-1 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in ord-central-1 is running behind schedule.
False-positive rate has returned to nominal. Affected travelers have been re-cleared.
A watchlist update has been rolled back. Holds are being released.
An increased rate of valid travelers are being held at the entry boundary due to watchlist false positives.
Egress is operating normally in syd-pacific-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in syd-pacific-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
Recalibration complete. All portals in nrt-asia-1 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in nrt-asia-1 is running behind schedule.
Recalibration complete. All portals in ord-central-1 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in ord-central-1 is running behind schedule.
All incorrect charges have been refunded. No further action is required.
Affected accounts have been identified. Refunds are being issued.
A small number of accounts have been charged temporal handling fees on provisional credit drawdowns that should be exempt.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Latency in syd-pacific-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in syd-pacific-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in syd-pacific-1. Median latency is unaffected. No impact to ongoing traversals.
Egress is operating normally in iad-east-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in iad-east-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
All handoffs into dfw-south-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into dfw-south-1 are failing. Active travelers in dfw-south-1 are unaffected, but new operator-assisted operations cannot complete.
Dispatch to syd-pacific-1 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to syd-pacific-1 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into syd-pacific-1 are failing to complete. Stuck-in-portal events in this region are being queued.
Scales have been recalibrated. Mass-limit checks are operating correctly.
A calibration error in the boundary scale has been identified. Affected portals are being held.
Some travelers in iad-east-1 are being rejected at the entry boundary on mass-limit checks. Affected weight range: 65–80 kg.
Voucher validation is operating within nominal latency.
The validation cache has been flushed. Latency is decreasing.
Voucher code validation is timing out for a subset of requests.
Latency in iad-east-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in iad-east-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in iad-east-1. Median latency is unaffected. No impact to ongoing traversals.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Recalibration complete. All portals in fra-europe-2 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in fra-europe-2 is running behind schedule.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Dispatch to ord-central-1 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to ord-central-1 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into ord-central-1 are failing to complete. Stuck-in-portal events in this region are being queued.
Custody-held travelers from this event will be reconciled at the close of the current billing cycle. Affected accounts will receive a notice from their operator.
Duplicate rate has returned to nominal. No additional travelers have been placed in custody.
The duplicate rate has been traced to a stuck inter-timeline reconciliation worker. We are restarting the worker.
We are seeing an elevated rate of duplicate emergence events. Affected travelers are being placed in custody hold per protocol.
All incorrect charges have been refunded. No further action is required.
Affected accounts have been identified. Refunds are being issued.
A small number of accounts have been charged temporal handling fees on provisional credit drawdowns that should be exempt.
Dispatch to syd-pacific-1 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to syd-pacific-1 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into syd-pacific-1 are failing to complete. Stuck-in-portal events in this region are being queued.
Voucher validation is operating within nominal latency.
The validation cache has been flushed. Latency is decreasing.
Voucher code validation is timing out for a subset of requests.
Backlog cleared. Anomaly review is operating within SLA.
Additional reviewers have been added. The backlog is decreasing.
The anomaly review backlog has exceeded its nominal threshold.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
False-positive rate has returned to nominal. Affected travelers have been re-cleared.
A watchlist update has been rolled back. Holds are being released.
An increased rate of valid travelers are being held at the entry boundary due to watchlist false positives.
Queue depth has returned to nominal. Dispatch SLAs are being met.
Additional operators have been brought online in fra-europe-2. The queue is draining.
Recovery dispatch queue depth has exceeded nominal thresholds. P3 and P4 dispatches may experience elevated wait times.
The endpoint is now returning 410 Gone as expected.
A regression in error handling has been identified. The endpoint should be returning 410 Gone, not 500. Fix is being deployed.
The phlogiston reserves endpoint is returning 500 errors. Note: this is a legacy endpoint and is no longer accepting deposits per the 1850 deprecation.
Scales have been recalibrated. Mass-limit checks are operating correctly.
A calibration error in the boundary scale has been identified. Affected portals are being held.
Some travelers in iad-east-1 are being rejected at the entry boundary on mass-limit checks. Affected weight range: 65–80 kg.
The endpoint is now returning 410 Gone as expected.
A regression in error handling has been identified. The endpoint should be returning 410 Gone, not 500. Fix is being deployed.
The phlogiston reserves endpoint is returning 500 errors. Note: this is a legacy endpoint and is no longer accepting deposits per the 1850 deprecation.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
All handoffs into nrt-asia-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into nrt-asia-1 are failing. Active travelers in nrt-asia-1 are unaffected, but new operator-assisted operations cannot complete.
All SWIFT-T transfers are succeeding. The gateway has confirmed restoration.
The gateway is undergoing maintenance in the originating timeline. We are routing around it.
A correspondent-bank gateway is intermittently returning 503 errors on SWIFT-T transfers.
All handoffs into fra-europe-2 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into fra-europe-2 are failing. Active travelers in fra-europe-2 are unaffected, but new operator-assisted operations cannot complete.
Latency in nrt-asia-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in nrt-asia-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in nrt-asia-1. Median latency is unaffected. No impact to ongoing traversals.
Queue depth has returned to nominal. Dispatch SLAs are being met.
Additional operators have been brought online in nrt-asia-1. The queue is draining.
Recovery dispatch queue depth has exceeded nominal thresholds. P3 and P4 dispatches may experience elevated wait times.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
Validation latency is back to nominal.
A database index is being rebuilt.
Traveler manifest validation is running 3-5x slower than nominal in sjc-west-1.
All SWIFT-T transfers are succeeding. The gateway has confirmed restoration.
The gateway is undergoing maintenance in the originating timeline. We are routing around it.
A correspondent-bank gateway is intermittently returning 503 errors on SWIFT-T transfers.
Egress is operating normally in syd-pacific-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in syd-pacific-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
Scales have been recalibrated. Mass-limit checks are operating correctly.
A calibration error in the boundary scale has been identified. Affected portals are being held.
Some travelers in nrt-asia-1 are being rejected at the entry boundary on mass-limit checks. Affected weight range: 65–80 kg.
Validation latency is back to nominal.
A database index is being rebuilt.
Traveler manifest validation is running 3-5x slower than nominal in dfw-south-1.
Reconciliation has completed. No travelers were released from custody as a result of this delay.
Scheduled custody hold reconciliation is running behind. Holds will continue to be honored.
All handoffs into nrt-asia-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into nrt-asia-1 are failing. Active travelers in nrt-asia-1 are unaffected, but new operator-assisted operations cannot complete.
All SWIFT-T transfers are succeeding. The gateway has confirmed restoration.
The gateway is undergoing maintenance in the originating timeline. We are routing around it.
A correspondent-bank gateway is intermittently returning 503 errors on SWIFT-T transfers.
The endpoint is now returning 410 Gone as expected.
A regression in error handling has been identified. The endpoint should be returning 410 Gone, not 500. Fix is being deployed.
The phlogiston reserves endpoint is returning 500 errors. Note: this is a legacy endpoint and is no longer accepting deposits per the 1850 deprecation.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Validation latency is back to nominal.
A database index is being rebuilt.
Traveler manifest validation is running 3-5x slower than nominal in lhr-europe-1.
Reconciliation has completed. No travelers were released from custody as a result of this delay.
Scheduled custody hold reconciliation is running behind. Holds will continue to be honored.
Latency in dfw-south-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in dfw-south-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in dfw-south-1. Median latency is unaffected. No impact to ongoing traversals.
All incorrect charges have been refunded. No further action is required.
Affected accounts have been identified. Refunds are being issued.
A small number of accounts have been charged temporal handling fees on provisional credit drawdowns that should be exempt.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Custody-held travelers from this event will be reconciled at the close of the current billing cycle. Affected accounts will receive a notice from their operator.
Duplicate rate has returned to nominal. No additional travelers have been placed in custody.
The duplicate rate has been traced to a stuck inter-timeline reconciliation worker. We are restarting the worker.
We are seeing an elevated rate of duplicate emergence events. Affected travelers are being placed in custody hold per protocol.
Custody-held travelers from this event will be reconciled at the close of the current billing cycle. Affected accounts will receive a notice from their operator.
Duplicate rate has returned to nominal. No additional travelers have been placed in custody.
The duplicate rate has been traced to a stuck inter-timeline reconciliation worker. We are restarting the worker.
We are seeing an elevated rate of duplicate emergence events. Affected travelers are being placed in custody hold per protocol.
Egress is operating normally in lhr-europe-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in lhr-europe-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
All handoffs into iad-east-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into iad-east-1 are failing. Active travelers in iad-east-1 are unaffected, but new operator-assisted operations cannot complete.
Validation latency is back to nominal.
A database index is being rebuilt.
Traveler manifest validation is running 3-5x slower than nominal in syd-pacific-1.
All handoffs into nrt-asia-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into nrt-asia-1 are failing. Active travelers in nrt-asia-1 are unaffected, but new operator-assisted operations cannot complete.
The endpoint is now returning 410 Gone as expected.
A regression in error handling has been identified. The endpoint should be returning 410 Gone, not 500. Fix is being deployed.
The phlogiston reserves endpoint is returning 500 errors. Note: this is a legacy endpoint and is no longer accepting deposits per the 1850 deprecation.
Egress is operating normally in sjc-west-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in sjc-west-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
Reconciliation has completed. No travelers were released from custody as a result of this delay.
Scheduled custody hold reconciliation is running behind. Holds will continue to be honored.
Dispatch to fra-europe-2 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to fra-europe-2 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into fra-europe-2 are failing to complete. Stuck-in-portal events in this region are being queued.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Egress is operating normally in iad-east-1. Recovery-routed travelers from this event are receiving operator follow-up.
Recalibration complete. Traversals are succeeding. Monitoring closely.
A geometry calibration drift has been identified. Affected thresholds are being held while we recalibrate.
A subset of egress thresholds in iad-east-1 are rejecting otherwise valid traversals. Affected travelers are being routed to the recovery queue.
Latency in ord-central-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in ord-central-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in ord-central-1. Median latency is unaffected. No impact to ongoing traversals.
Latency in nrt-asia-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in nrt-asia-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in nrt-asia-1. Median latency is unaffected. No impact to ongoing traversals.
The endpoint is now returning 410 Gone as expected.
A regression in error handling has been identified. The endpoint should be returning 410 Gone, not 500. Fix is being deployed.
The phlogiston reserves endpoint is returning 500 errors. Note: this is a legacy endpoint and is no longer accepting deposits per the 1850 deprecation.
All SWIFT-T transfers are succeeding. The gateway has confirmed restoration.
The gateway is undergoing maintenance in the originating timeline. We are routing around it.
A correspondent-bank gateway is intermittently returning 503 errors on SWIFT-T transfers.
All incorrect charges have been refunded. No further action is required.
Affected accounts have been identified. Refunds are being issued.
A small number of accounts have been charged temporal handling fees on provisional credit drawdowns that should be exempt.
Queue depth has returned to nominal. Dispatch SLAs are being met.
Additional operators have been brought online in ord-central-1. The queue is draining.
Recovery dispatch queue depth has exceeded nominal thresholds. P3 and P4 dispatches may experience elevated wait times.
Recalibration complete. All portals in dfw-south-1 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in dfw-south-1 is running behind schedule.
Sign-in is fully restored. We apologize for the impact.
Traced to a recent change in the identity preservation check. Reverting now.
Accounts with one or more active custody holds may be unable to sign in.
Console availability has been stable for over 30 minutes.
Console is now available. Monitoring for recurrence.
A console bootstrapping issue has been identified.
Some operators are reporting intermittent unavailability of the operator console.
Validation latency is back to nominal.
A database index is being rebuilt.
Traveler manifest validation is running 3-5x slower than nominal in nrt-asia-1.
Scales have been recalibrated. Mass-limit checks are operating correctly.
A calibration error in the boundary scale has been identified. Affected portals are being held.
Some travelers in dfw-south-1 are being rejected at the entry boundary on mass-limit checks. Affected weight range: 65–80 kg.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
Recalibration complete. All portals in nrt-asia-1 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in nrt-asia-1 is running behind schedule.
Recalibration complete. All portals in fra-europe-2 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in fra-europe-2 is running behind schedule.
Scales have been recalibrated. Mass-limit checks are operating correctly.
A calibration error in the boundary scale has been identified. Affected portals are being held.
Some travelers in syd-pacific-1 are being rejected at the entry boundary on mass-limit checks. Affected weight range: 65–80 kg.
Queue depth has returned to nominal. Dispatch SLAs are being met.
Additional operators have been brought online in dfw-south-1. The queue is draining.
Recovery dispatch queue depth has exceeded nominal thresholds. P3 and P4 dispatches may experience elevated wait times.
Latency in nrt-asia-1 has returned to expected levels.
Recalibration complete. Latency is returning to baseline. We are continuing to monitor.
A transit-layer worker in nrt-asia-1 is rebalancing across operator pools. Recalibration is in progress.
We are investigating reports of elevated p99 transit latency in nrt-asia-1. Median latency is unaffected. No impact to ongoing traversals.
Dispatch to iad-east-1 has been stable. Queued recoveries from this event have all been processed.
Secondary handoff is active. Recoveries are completing. Monitoring closely.
Operator handoff to iad-east-1 is failing. We are bringing up a secondary handoff path.
Recovery dispatches into iad-east-1 are failing to complete. Stuck-in-portal events in this region are being queued.
Validation latency is back to nominal.
A database index is being rebuilt.
Traveler manifest validation is running 3-5x slower than nominal in dfw-south-1.
Recalibration complete. All portals in nrt-asia-1 have been verified.
Recalibration is now running. Estimated completion in 30 minutes.
Scheduled portal recalibration in nrt-asia-1 is running behind schedule.
All handoffs into dfw-south-1 have been stable for the past 90 minutes.
Handoffs are succeeding again. Monitoring closely for related issues.
A timeline-perimeter authentication failure has been traced to an expired certificate. Renewal is in progress.
All inter-timeline operator handoffs into dfw-south-1 are failing. Active travelers in dfw-south-1 are unaffected, but new operator-assisted operations cannot complete.
All SWIFT-T transfers are succeeding. The gateway has confirmed restoration.
The gateway is undergoing maintenance in the originating timeline. We are routing around it.
A correspondent-bank gateway is intermittently returning 503 errors on SWIFT-T transfers.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Receipts are delivering within target. Backlog cleared.
A backlog in the receipt-delivery worker is being drained.
Traversal receipts are being delivered slower than the 30-second target.
All incorrect charges have been refunded. No further action is required.
Affected accounts have been identified. Refunds are being issued.
A small number of accounts have been charged temporal handling fees on provisional credit drawdowns that should be exempt.
Cross-timeline transfers have been operating normally for the past hour.
Transfers have been resumed at reduced throughput. We are monitoring for further anomalies.
Review is in progress. We expect to resume within 90 minutes.
We have paused all cross-timeline credit transfers pending a review of recent reconciliation anomalies. Local-region transfers are unaffected.
Voucher validation is operating within nominal latency.
The validation cache has been flushed. Latency is decreasing.
Voucher code validation is timing out for a subset of requests.
All timestamps in UTC. Incident IDs are issued on first investigation. Resolved incidents remain visible for 14 days. For real-time alerts, subscribe via hello@portaluse.com.