From the AWS edition of November 7, 2026
ModelBank: Amazon Bedrock degraded about 2.4 hours on Nov 6 as US-WEST-2 EC2/EBS launch failures hit dependent services
ModelBank.ai · Independent AI service availability monitoring · AWS US-West-2 (Oregon) commercial Region; GovCloud not involved per source
- Publisher
- ModelBank outage archive
- Original publication
- 2026-11-06
- Source retrieved
- 2026-11-08
- Event date
- 2026-11-06
What happened
ModelBank reports Amazon Bedrock had degraded performance on November 6, 2026 between 22:51 and 01:12 UTC (about 2.4 hours; 4:51–7:12 PM CT), mapped to one official AWS incident, 'Elevated Launch Failures' in US-WEST-2. Quoted AWS updates attribute the issue to a subsystem supporting EBS volumes needed during EC2 instance launch, affecting all four Oregon AZs and services that instantiate new instances (for example DataSync and AWS Backup); AWS advised customers not to mutate running instances. The resolved notice gives 2:35–4:21 PM PST. ModelBank's own probes detected degradation for about one hour. It reports 100.00% measured availability over 30 days and seven days with an outage or degradation in the last 90 days.
Why it matters
SLED Bedrock workloads hosted in US-West-2 can be affected by underlying EC2/EBS events; reinforces cross-Region or GovCloud cross-Region inference and resilience planning for constituent-facing AI.
Evidence and measured results
Third-party monitoring page combining its probes with quoted AWS status text; not an AWS post-incident report.
Limitations and uncertainty
Which Bedrock functions degraded is not specified; probe methodology not detailed; times differ between official window (2:35–4:21 PM PST) and ModelBank window; no AWS root-cause report.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Constituent-facing AI services can degrade when underlying regional AWS infrastructure has incidents.
- Stakeholders
- Agency CIO
- Service operations lead
- Constituent services director
- Discovery questions
- Which Region hosts your Bedrock workloads?
- Is cross-Region inference allowed under data rules?
- What is the non-AI fallback?
- Value hypothesis
- Resilience design can limit resident-facing disruption during regional incidents; not quantified here.
- Potential engagement
- Resilience review and game-day test for one AI service.
- Unsupported claims
- GovCloud impact
- Specific Bedrock features affected
- Root cause beyond AWS status text
Pre-sales engineering
Role takeaway
- Fit
- Relevant to US-West-2 Bedrock workloads; general resilience lesson elsewhere.
- Architecture and integration
- Cross-Region inference profiles, timeouts, circuit breakers, fallback paths.
- Prerequisites
- Region inventory
- Data-residency rules
- CloudWatch alarms
- Constraints
- Residency limits on cross-Region routing
- Third-party monitoring data
- Security
- Availability only; no security impact reported.
- Proof of value
- Game-day shows graceful degradation
- Alarm latency measured
Delivery
Role takeaway
- Work
- Create AI incident playbook and fallback path.
- Dependencies
- CloudWatch
- AWS Health
- Fallback content
- Ownership
- Service operations team.
- Skills and adoption
- Incident response for AI services.
- Governance checkpoints
- Cross-Region routing approval
- Fallback messaging review
- Acceptance criteria
- Proposed: alarms within five minutes
- Proposed: fallback activates in game-day
- Risks
- Untested fallback
- Residency conflict
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Dependency of AI services on regional compute/storage control planes; supports multi-Region inference profiles and graceful degradation for AI front ends.
Governance
Who approves, reviews and stays accountable for outcomes?
Agencies should define AI service availability expectations and fallback procedures in runbooks and contracts.
Security and privacy
What data, permissions and controls need testing?
Availability risk only; no security impact reported.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Constituent-facing AI assistants should have non-AI fallback paths during degradation.
Procurement
What should contracts, pricing and exit terms secure?
Consider availability commitments and incident communication terms when procuring AI services.
Operating model
Which teams own the service once it runs?
Operations teams need monitoring of Bedrock-dependent workflows and incident playbooks.
Publication history
- 2026-11-07AWS · Issue 107 resources
Stable resource ID: modelbank-bedrock-us-west-2-degradation-20261106