Monday, June 16, 2025
Home Blog

will they have permanent spots?

0


The Golden State Valkyries have resigned Chloe Bibby and Kaitlyn Chen, who each joined the team this preseason, for at least the coming two weeks as several players participate in EuroBasket. Golden State did not specify contract lengths for Bibby or Chen in the team’s press release.

Both players will be immediately available for the team’s June 17 game against the Dallas Wings. Bibby will wear number 55 and Chen will wear number 2 for Golden State.

Bibby, who hails from the Australian National Team, averaged 5.0 points, 1.5 rebounds, and a 37.5 field goal percentage in two preseason games for the Valkyries ahead of this season. Chen, who helped UConn win the national championship this year, was selected by the Valkyries as the No. 30 overall pick in this year’s draft and added two points, three rebounds and one assist to the team in 13 minutes of preseasn play.

Kaitlyn Chen was set to participate in 3XBA

The news likely throws a wrench in Chen’s plans to participate in 3XBA this month — something that’s positive for her, but perhaps not so much for her team. She was slated to play in the Spokane Hoop Fest, which kicks off on June 28, 2025.

FIBA 3XBA is the only professional FIBA 3×3 league in the United States. Like Athletes Unlimited and Unrivaled, the league offers women’s basketball players the opportunity to play the sport outside of the WNBA, and without having to travel overseas.

The gameplay is like the 3×3 format in the Olympics — 10-minute games, 12-second shot clock. Players who participate in 3XBA games also earn points toward their own FIBA ranking, which can help qualify the United States for the Olympics.

The Valkyries originally signed Chloe Bibby in February

Golden State picked up Bibby for the first time in early February 2025. At the time, Bibby was averaging 18 points per game and shooting 47% from the 3-point line for Uni Girona CB in EuroCup.

She also has plenty of experience playing in the US at the collegiate level and spent time at both Mississippi State and Maryland.

Golden State has holes to fill

The Valkyries are missing a sizeable portion of the team’s roster due to the EuroBasket tournament, which begins June 18. The list of qualified countries includes France, Serbia, Spain, Sweden, Turkey, Portugal, Great Britain, Lithuania, Switzerland, Croatia, Slovakia, Latvia, Hungary, Belgium, Montenegro, and Slovenia.

Julia Vanloo and Kayra Linskens will both play for Belgium this month (and Linskens has already announced she will not return to Golden State after the tournament), and Janelle Salaun will represent France. Cecilia Zandalasini will play for Italy, and it’s unknown if Temi Fagbenle will remain in the US or play for Great Britain in this year’s contest.



Source link

Valkyries re-sign former UConn guard Kaitlyn Chen, forward Chloe Bibby after waiving them in the preseason

0


A month after getting waived, Kaitlyn Chen is back with the Golden State Valkyries.

In addition, Golden State has re-signed Chloe Bibby, an Australian forward who went undrafted out Maryland in 2022. Bibby signed a training camp contract with the team last month, but was also waived prior to the regular season.

Advertisement

Both players will join the team immediately, and will play against the Dallas Wings on Tuesday.

The move comes as several Valkyries players — including guard Julie Vanloo (Belgium) and center Temi Fagbenle (Great Britain) — have left the team to compete in the FIBA EuroBasket tournament. The tournament, which begins this week, runs through the end of the month.

Laeticia Amihere, another training camp player, was also re-signed by the team earlier this month, likely in connection with the FIBA departures. It is unclear whether Chen, Bibby and Amihere will be released when those players return.

Chen was drafted by Golden State in the third round of the WNBA Draft, after going to the event to support her teammate Paige Bueckers. She played with the Valkyries throughout training camp and played in two preseason games before being waived.

Now, Chen will return to Golden State — and will compete against Bueckers in her first WNBA regular-season game.



Source link

‘Let’s go to pound town’

0


Dakota Johnson does not need to prepare for intimate scenes; she’s already “always psyched up for sex.”

The star, whose breakout role was Anastasia Steele in the spicy 50 Shades of Grey franchise, appeared on Tuesday’s episode of Amy Poehler‘s Good Hang podcast to chat about her upcoming romance comedy Materialists when the topic turned to how she prepared for sex scenes.

“I don’t have to. I’m, like, always psyched up for sex,” Johnson quipped to Poehler.

“F— yeah,” Poehler said, as the two laughed over the phrasing.

“‘Psyched up?’ Is that a thing?” Johnson asked. “Let’s go to pound town?”

On a more serious note, Johnson recalled how she recently worked on a film a few months ago and it was the first time she had ever worked with an intimacy coordinator.

“And she was really great,” Johnson said. “It was so cool because I’m so used to, just you know, like, it’s a sex scene. It’s not sexy. It doesn’t feel good.”

She shared that character work was integral to preparing for the scenes.

Universal Pictures Dakota Johnson and Jamie Dornan in ‘Fifty Shades Freed’

“First, it depends on who the character is and who the character’s supposed to be to the audience,” Johnson said. “Is she like a super idolized hot girl? Is she a housewife? Is she lonely? Is she scared? Is she conservative?”

“Certain prep would go into it,” Johnson added. “I want to feel good in my body if I’m showing my body.” Johnson, the daughter of actor parents Melanie Griffith and Don Johnson, also said that her famous mother helped instill in her the confidence required for such intimate and vulnerable scenes.

“My mom raised me to be really proud of my body and love my body,” Johnson said. “So I’ve always felt so grateful for that, especially in my work because I can use it and it feels real. She was very honest and open about body stuff, like getting my period. She also talked to me about sex and how precious and important it is.”

Want more movie news? Sign up for Entertainment Weekly‘s free newsletter to get the latest trailers, celebrity interviews, film reviews, and more.

Johnson added, “So I guess in my work, it’s something that I feel brave with and that I feel, when it’s used the right way in a story.”

The star is gearing up for the release of Materialists (in theaters June 13), loosely inspired by director-writer Celine Song’s side hustle as a New York City matchmaker when she was a struggling playwright in need of extra income. Johnson plays Lucy, a skilled liaison for lonely hearts at a successful matchmaking firm who isn’t as proficient when it comes to her own love life. She’s torn between her imperfect ex, struggling actor John (Chris Evans), and the perfect and wealthy Harry (Pedro Pascal).

Taylor Hill/Getty Melanie Griffith and Dakota Johnson in 2017

Taylor Hill/Getty

Melanie Griffith and Dakota Johnson in 2017

“She’s at a very interesting time in her life where she’s sort of teetering between two worlds,” Johnson previously told Entertainment Weekly of her character arc. “A lot of what she does is very surface-level stuff. I think for a long time she has been very comfortable in that because it means she doesn’t have to actually go inward and look at herself and what she wants for her own life.”

“It’s a story of bravery, really, and fear,” she added. “Allowing yourself to be loved is scary, and really loving another person is scary . . . a woman having the courage to open her heart is what I loved about it.”

Read the original article on Entertainment Weekly



Source link

Morning fire on James Street burns apartment building; those inside escaped

0


At least two apartments on James Street near the Interstate 5 exit at Lakeway were scorched in a Friday morning fire.

Bellingham Fire Department and Bellingham Police Department responded to a residential fire around 11 a.m. June 13 at the 1400 block of James Street. Crews put out the fire in about 30 minutes.

One person was rescued from a second-story balcony, who left the scene. Another person jumped from a second-story window. That individual and another were transported to the hospital, said Dustin Michaelis, of BFD.

Reporters on scene witnessed two apartments smoking and charred, with broken glass windows and melted patio furniture. At least two more apartments are in the building. Fire alarms could be heard blaring in the two-floor building.

Bellingham firefighters get hosed down after battling an apartment building fire. (Andy Bronson/Cascadia Daily News)

Neighbor Neil Marks, 38, said he had heard his dogs barking and assumed someone was at the door. Instead, when he looked out his window, the ground-floor apartment next to his house was in flames.

“I called 911 and grabbed my fire extinguisher,” he said, adding he sprayed down trees overhanging in the backyard and alley to make sure flames didn’t jump.

Neighbor Lexi Kok, 35, said she saw multiple fire trucks and ran into a friend who is a firefighter when they were notified the building was on fire. She knows at least one man who lives in the building.

“I came over to see if he was OK, but he was clearly not home,” she said.

The cause of the fire remains under investigation.

This is a developing story. Check back later for more.

Chris and Neal Marks watch and record as firefighters battle an apartment building fire next door. (Andy Bronson/Cascadia Daily News)

Annie Todd is CDN’s criminal justice/enterprise reporter; reach her at annietodd@cascadiadaily.com; 360-922-3090 ext. 130.



Source link

Men’s College World Series 2025: Coastal Carolina, Oregon State notch wins, LSU on pace for record Jell-O shot sales

0


The 2025 Men’s College World Series kicked off Friday, with No. 13 Coastal Carolina earning the first win of the tournament over Arizona and No. 8 Oregon State outlasting Louisville in the late game.

Oregon State 4, Louisville 3

Oregon State had a win in hand entering the ninth inning — and didn’t let some misadventures stop them from advancing in the winner’s bracket.

Advertisement

Gavin Turley hit a walk-off double to give his team a 4-3 win after the Beavers blew a two-run lead in the top of the ninth. Aiva Arquette, one of the top prospects for the 2025 MLB Draft, set it up with a one-out single, then motored first-to-home on Turley’s line drive into left field.

Turley and Arquette were the heroes of the bottom of the ninth and the goats of the top. Defensive blunders from both players allowed Louisville to tie the game, with a missed dive from Turley turning into a triple and a bad throw from Arquette giving the Cardinals another man on third, who later scored.

The miscues nearly spoiled a great outing from star freshman Dax Whitney, who struck out nine across 5 1/3 innings while allowing three hits and a single run. The lanky right-hander with big heat and a bigger curveball outlasted the Cardinals’ Patrick Forbes in a battle of future MLB Draft picks.

Whitney was ranked as the No. 56 prospect of the 2024 MLB Draft by MLB Pipeline. The No. 57 prospect, Boston Bateman, got $2.5 million from the San Diego Padres. Whitney has more than helped his stock this season and now projects as a future first-round pick after earning second-team Freshman All-America honors.

Advertisement

Curiously, the first 15 hits of this game were all singles, with Rose getting the first extra-base hit of the game with his leadoff triple in the ninth inning.

The Beavers got their first runs when they opened the bottom of the fourth with four straight singles. Louisville got one run back in the sixth with its own rally but then handed Oregon State an insurance run when shortstop Alex Alicea booted a potential double-play ball with the bases loaded.

With the victory, Oregon State advances to face Coastal Carolina in the next round, while Louisville will get Arizona in the loser’s bracket on Sunday.

Coastal Carolina 7, Arizona 4

The Chanticleers, who came into the CWS with the best record in Division I, overcame a 4-4 tie with a few clutch doubles in the bottom of the eighth to keep their 24-game winning streak alive.

Advertisement

It was a quiet first inning for both teams. But in the second inning, Coastal Carolina had a huge opportunity, loading the bases off a muffed infield catch by Arizona pitcher Owen Kramkowski. Outfielder Wells Sykes took advantage, hitting a two-run single to put the Chanticleers on the board.

Arizona came alive in the top of the fourth, starting with a solo homer from shortstop Mason White. Then the Wildcats hit back-to-back doubles, sending catcher Adonys Guzman home to tie the game 2-2.

In the bottom of the fifth, a single from Chanticleers right fielder Blagen Pado sent second baseman Blake Barthol home for a 3-2 lead.

Coastal Carolina is known for getting hit by pitches; the team has been hit by an NCAA-leading 170 pitches this season. But in the sixth inning, it was Arizona who took advantage of getting hit. Chanticleers reliever Cameron Flukey hit three batters, allowing the Wildcats to load the bases and score a game-tying run before they recorded an out.

Advertisement

Then a grounder from second baseman Garen Caulfield sent White home to give Arizona a 4-3 lead.

In the bottom of the sixth, Chanticleers catcher Caden Bodine drove in a run to make it 4-4.

The two teams stayed locked in a tie for the next two innings off some strong defensive play, with Flukey settling in. In the bottom of the eighth, with the Chanticleers sitting on two outs, it looked like the game would come down to the final inning. Then Coastal Carolina’s offense broke through.

It started with Sykes getting on second on a hit that landed right on the line. Left fielder Sebastian Alexander then hit an RBI single to send Sykes home for a 5-4 lead. Another huge double from Barthol sent Alexander and Bodine, who was intentionally walked, home to give the Chanticleers a 7-4 lead heading into the ninth.

Arizona wasn’t done yet, as designated hitter Andrew Cain earned a double with some bold running, and first baseman Tommy Splaine got a base hit. But a huge double-play ended the game and sent Coastal Carolina to the winners’ bracket.

Advertisement

Jell-O Shot challenge update

The men’s College World Series has one of the most entertaining side plots of any NCAA championship: the Jell-O shot competition at Rocco’s, where patrons compete annually to see which school’s fan base can consume the most Jell-O shots.

LSU, which set the record with 68,888 Jell-O shots purchased in 2023, is off to an early lead after the first day of the MCWS, with a monstrous 4,410 shots as of 10 p.m. CT. That tally is far ahead of last year’s pace, setting LSU up for another record victory.

However, Murray State and Coastal Carolina are also on a roll, coming in at 2,180 and 1,753 shots, respectively, after a back-and-forth Friday.

Regardless of who wins, all three schools are currently on pace to break LSU’s 2023 record.



Source link

“Different Levels of Authenticity”: How ‘Arcane’s Showrunner Made Sure Vi and Jinx’s Abilities Felt True to ‘League of Legends’

0


If there is one thing that Arcane is known for, it was able to craft meaningful stories for some League of Legends characters and champions that stay true to what was shown in the game but also something that audiences wanted to see. And according to showrunner Christian Linke, the show needed to find a balance, especially regarding Vi and Jinx.

In a recent interview with Deadline, Linke explained the balance needed to craft Vi (Hailee Steinfeld) and Jinx’s (Ella Purnell) stories. According to him, these two needed to showcase their fighting ability, which players see in the game, and craft a universal story that not only attracts viewers but is also authentic to the fans watching the show. In addition, he also revealed that they took into account player behavior when it came to character planning as part of their mission of authenticity.

“On one hand there was the character story,…



Source link

June 14: Aircraft Incident | Port of Seattle

0


Incident updates related to an aircraft on the runway at Seattle-Tacoma International Airport (SEA). Updates will be posted to this page as they become available. 

Updates

 

June 14, 2025, 3:19 p.m.

Runway 16R is expected to reopen shortly and SEA Airport will return to normal operations. Please continue to check in with your airline about your flight status.

June 14, 2025, 1:58 p.m.

All passengers have been deplaned. Suspect in custody. Center runway has been reopened. Investigation with aircraft continues with 16R still closed. Track your flight with your airline.

June 14, 2025, 1:34 p.m.

One suspect is in custody. Passengers will be deplaned and returned to terminal after security screening.

June 14, 2025 1:16 p.m.

Currently two runways are closed: 16R/16C. One runway is open: 16L. Travelers should monitor your airlines for your specific flight.

June 14, 2025 1:03 p.m.

Port of Seattle Police and Fire Departments are investigating a situation involving an aircraft on 16R/34L runway.

Traveler impacts

 Travelers should contact their airlines for updates on their specific flight.

How to stay up to date

Check this page for ongoing updates 

Follow us on social media:



Source link

Cloudflare service outage June 12, 2025

0


On June 12, 2025, Cloudflare suffered a significant service outage that affected a large set of our critical services, including Workers KV, WARP, Access, Gateway, Images, Stream, Workers AI, Turnstile and Challenges, AutoRAG, Zaraz, and parts of the Cloudflare Dashboard.

This outage lasted 2 hours and 28 minutes, and globally impacted all Cloudflare customers using the affected services. The cause of this outage was due to a failure in the underlying storage infrastructure used by our Workers KV service, which is a critical dependency for many Cloudflare products and relied upon for configuration, authentication and asset delivery across the affected services. Part of this infrastructure is backed by a third-party cloud provider, which experienced an outage today and directly impacted availability of our KV service.

We’re deeply sorry for this outage: this was a failure on our part, and while the proximate cause (or trigger) for this outage was a third-party vendor failure, we are ultimately responsible for our chosen dependencies and how we choose to architect around them.

This was not the result of an attack or other security event. No data was lost as a result of this incident. Cloudflare Magic Transit and Magic WAN, DNS, cache, proxy, WAF and related services were not directly impacted by this incident.

As a rule, Cloudflare designs and builds our services on our own platform building blocks, and as such many of Cloudflare’s products are built to rely on the Workers KV service. 

The following table details the impacted services, including the user-facing impact, operation failures, and increases in error rates observed:

Product/Service

Impact

Workers KV

Workers KV saw 90.22% of requests failing: any key-value pair not cached and that required to retrieve the value from Workers KV’s origin storage backends resulted in failed requests with response code 503 or 500. 

The remaining requests were successfully served from Workers KV’s cache (status code 200 and 404) or returned errors within our expected limits and/or error budget.

This did not impact data stored in Workers KV.

Access

Access uses Workers KV to store application and policy configuration along with user identity information.

During the incident Access failed 100% of identity based logins for all application types including Self-Hosted, SaaS and Infrastructure. User Identity information was unavailable to other services like WARP and Gateway during this incident. Access is designed to fail closed when it cannot successfully fetch policy configuration or a user’s identity. 

Active Infrastructure Application SSH sessions with command logging enabled failed to save logs due to a Workers KV dependency. 

Access’ System for Cross Domain Identity (SCIM) service was also impacted due to its reliance on Workers KV and Durable Objects (which depended on KV) to store user information. During this incident, user identities were not updated due to Workers KV updates failures. These failures would result in a 500 returned to identity providers. Some providers may require a manual re-synchronization but most customers would have seen immediate service restoration once Access’ SCIM service was restored due to retry logic by the identity provider.

Service authentication based logins (e.g. service token, Mutual TLS, and IP-based policies) and Bypass policies were unaffected. No Access policy edits or changes were lost during this time.

Gateway

This incident did not affect most Gateway DNS queries, including those over IPv4, IPv6, DNS over TLS (DoT), and DNS over HTTPS (DoH).

However, there were two exceptions:

DoH queries with identity-based rules failed. This happened because Gateway couldn’t retrieve the required user’s identity information.

Authenticated DoH was disrupted for some users. Users with active sessions with valid authentication tokens were unaffected, but those needing to start new sessions or refresh authentication tokens could not.

Users of Gateway proxy, egress, and TLS decryption were unable to connect, register, proxy, or log traffic.

This was due to our reliance on Workers KV to retrieve up-to-date identity and device posture information. Each of these actions requires a call to Workers KV, and when unavailable, Gateway is designed to fail closed to prevent traffic from bypassing customer-configured rules.

WARP

The WARP client was impacted due to core dependencies on Access and Workers KV, which is required for device registration and authentication. As a result, no new clients were able to connect or sign up during the incident.

Existing WARP client users sessions that were routed through the Gateway proxy experienced disruptions, as Gateway was unable to perform its required policy evaluations.

Additionally, the WARP emergency disconnect override was rendered unavailable because of a failure in its underlying dependency, Workers KV.

Consumer WARP saw a similar sporadic impact as the Zero Trust version.

Dashboard

Dashboard user logins and most of the existing dashboard sessions were unavailable. This was due to an outage affecting Turnstile, DO, KV, and Access. The specific causes for login failures were:

Standard Logins (User/Password): Failed due to Turnstile unavailability.

Sign-in with Google (OIDC) Logins: Failed due to a KV dependency issue.

SSO Logins: Failed due to a full dependency on Access.

The Cloudflare v4 API was not impacted during this incident.

Challenges and Turnstile

The Challenge platform that powers Cloudflare Challenges and Turnstile saw a high rate of failure and timeout for siteverify API requests during the incident window due to its dependencies on Workers KV and Durable Objects.

We have kill switches in place to disable these calls in case of incidents and outages such as this. We activated these kill switches as a mitigation so that eyeballs are not blocked from proceeding. Notably, while these kill switches were active, Turnstile’s siteverify API (the API that validates issued tokens) could redeem valid tokens multiple times, potentially allowing for attacks where a bad actor might try to use a previously valid token to bypass. 

There was no impact to Turnstile’s ability to detect bots. A bot attempting to solve a challenge would still have failed the challenge and thus, not receive a token. 

Browser Isolation

Existing Browser Isolation sessions via Link-based isolation were impacted due to a reliance on Gateway for policy evaluation.

New link-based Browser Isolation sessions could not be initiated due to a dependency on Cloudflare Access. All Gateway-initiated isolation sessions failed due its Gateway dependency.

Images

Batch uploads to Cloudflare Images were impacted during the incident window, with a 100% failure rate at the peak of the incident. Other uploads were not impacted.

Overall image delivery dipped to around 97% success rate. Image Transformations were not significantly impacted, and Polish was not impacted.

Stream

Stream’s error rate exceeded 90% during the incident window as video playlists were unable to be served. Stream Live observed a 100% error rate.

Video uploads were not impacted.

Realtime

The Realtime TURN (Traversal Using Relays around NAT) service uses KV and was heavily impacted. Error rates were near 100% for the duration of the incident window.

The Realtime SFU service (Selective Forwarding Unit) was unable to create new sessions, although existing connections were maintained. This caused a reduction to 20% of normal traffic during the impact window. 

Workers AI

All inference requests to Workers AI failed for the duration of the incident. Workers AI depends on Workers KV for distributing configuration and routing information for AI requests globally.

Pages & Workers Assets

Static assets served by Cloudflare Pages and Workers Assets (such as HTML, JavaScript, CSS, images, etc) are stored in Workers KV, cached, and retrieved at request time. Workers Assets saw an average error rate increase of around 0.06% of total requests during this time. 

During the incident window, Pages error rate peaked to ~100% and all Pages builds could not complete. 

AutoRAG

AutoRAG relies on Workers AI models for both document conversion and generating vector embeddings during indexing, as well as LLM models for querying and search. AutoRAG was unavailable during the incident window because of the Workers AI dependency.

Durable Objects

SQLite-backed Durable Objects share the same underlying storage infrastructure as Workers KV. The average error rate during the incident window peaked at 22%, and dropped to 2% as services started to recover.

Durable Object namespaces using the legacy key-value storage were not impacted.

D1

D1 databases share the same underlying storage infrastructure as Workers KV and Durable Objects.

Similar to Durable Objects, the average error rate during the incident window peaked at 22%, and dropped to 2% as services started to recover.

Queues & Event Notifications

Queues message operations including–pushing and consuming–were unavailable during the incident window.

Queues uses KV to map each Queue to underlying Durable Objects that contain queued messages.

Event Notifications use Queues as their underlying delivery mechanism.

AI Gateway

AI Gateway is built on top of Workers and relies on Workers KV for client and internal configurations. During the incident window, AI Gateway saw error rates peak at 97% of requests until dependencies recovered.

CDN

Automated traffic management infrastructure was operational but acted with reduced efficacy during the impact period. In particular, registration requests from Zero Trust clients increased substantially as a result of the outage.

The increase in requests imposed additional load in several Cloudflare locations, triggering response from automated traffic management. In response to these conditions, systems rerouted incoming CDN traffic to nearby locations, reducing impact to customers. There was a portion of traffic that was not rerouted as expected and is under investigation. CDN requests impacted by this issue would experience elevated latency, HTTP 499 errors, and / or HTTP 503 errors. Impacted Cloudflare service areas included São Paulo, Philadelphia, Atlanta, and Raleigh.

Workers / Workers for Platforms

Workers and Workers for Platforms rely on a third party service for uploads. During the incident window, Workers saw an overall error rate peak to ~2% of total requests. Workers for Platforms saw an overall error rate peak to ~10% of total requests during the same time period. 

Workers Builds (CI/CD)
 

Starting at 18:03 UTC Workers builds could not receive new source code management push events due to Access being down.

100% of new Workers Builds failed during the incident window.

Browser Rendering

Browser Rendering depends on Browser Isolation for browser instance infrastructure.

Requests to both the REST API and via the Workers Browser Binding were 100% impacted during the incident window.

Zaraz

100% of requests were impacted during the incident window. Zaraz relies on Workers KV configs for websites when handling eyeball traffic. Due to the same dependency, attempts to save updates to Zaraz configs were unsuccessful during this period, but our monitoring shows that only a single user was affected.

Workers KV is built as what we call a “coreless” service which means there should be no single point of failure as the service runs independently in each of our locations worldwide. However, Workers KV today relies on a central data store to provide a source of truth for data. A failure of that store caused a complete outage for cold reads and writes to the KV namespaces used by services across Cloudflare.

Workers KV is in the process of being transitioned to significantly more resilient infrastructure for its central store: regrettably, we had a gap in coverage which was exposed during this incident. Workers KV removed a storage provider as we worked to re-architect KV’s backend, including migrating it to Cloudflare R2, to prevent data consistency issues (caused by the original data syncing architecture), and to improve support for data residency requirements.

One of our principles is to build Cloudflare services on our own platform as much as possible, and Workers KV is no exception. Many of our internal and external services rely heavily on Workers KV, which under normal circumstances helps us deliver the most robust services possible, instead of service teams attempting to build their own storage services. In this case, the cascading impact from the failure from Workers KV exacerbated the issue and significantly broadened the blast radius. 

Incident timeline and impact

The incident timeline, including the initial impact, investigation, root cause, and remediation, are detailed below. 

BLOG-2847 2

Workers KV error rates to storage infrastructure. 91% of requests to KV failed during the incident window.

BLOG-2847 1

Cloudflare Access percentage of successful requests. Cloudflare Access relies directly on Workers KV and serves as a good proxy to measure Workers KV availability over time.

All timestamps referenced are in Coordinated Universal Time (UTC).

Time

Event

2025-06-12 17:52

INCIDENT START
Cloudflare WARP team begins to see registrations of new devices fail and begin to investigate these failures and declares an incident.

2025-06-12 18:05

Cloudflare Access team received an alert due to a rapid increase in error rates.

Service Level Objectives for multiple services drop below targets and trigger alerts across those teams.

2025-06-12 18:06

Multiple service-specific incidents are combined into a single incident as we identify a shared cause (Workers KV unavailability). Incident priority upgraded to P1.

2025-06-12 18:21

Incident priority upgraded to P0 from P1 as severity of impact becomes clear.

2025-06-12 18:43

Cloudflare Access begins exploring options to remove Workers KV dependency by migrating to a different backing datastore with the Workers KV engineering team. This was proactive in the event the storage infrastructure continued to be down.

2025-06-12 19:09

Zero Trust Gateway began working to remove dependencies on Workers KV by gracefully degrading rules that referenced Identity or Device Posture state.

2025-06-12 19:32

Access and Device Posture force drop identity and device posture requests to shed load on Workers KV until third-party service comes back online.

2025-06-12 19:45

Cloudflare teams continue to work on a path to deploying a Workers KV release against an alternative backing datastore and having critical services write configuration data to that store.

2025-06-12 20:23

Services begin to recover as storage infrastructure begins to recover. We continue to see a non-negligible error rate and infrastructure rate limits due to the influx of services repopulating caches.

2025-06-12 20:25

Access and Device Posture restore calling Workers KV as third-party service is restored.

2025-06-12 20:28

IMPACT END 
Service Level Objectives return to pre-incident level. Cloudflare teams continue to monitor systems to ensure services do not degrade as dependent systems recover.

INCIDENT END
Cloudflare team see all affected services return to normal function. Service level objective alerts are recovered.

We’re taking immediate steps to improve the resiliency of services that depend on Workers KV and our storage infrastructure. This includes existing planned work that we are accelerating as a result of this incident.

This encompasses several workstreams, including efforts to avoid singular dependencies on storage infrastructure we do not own, improving the ability for us to recover critical services (including Access, Gateway and WARP) 

Specifically:

  • (Actively in-flight): Bringing forward our work to improve the redundancy within Workers KV’s storage infrastructure, removing the dependency on any single provider. During the incident window we began work to cut over and backfill critical KV namespaces to our own infrastructure, in the event the incident continued.

  • (Actively in-flight): Short-term blast radius remediations for individual products that were impacted by this incident so that each product becomes resilient to any loss of service caused by any single point of failure, including third party dependencies.

  • (Actively in-flight): Implementing tooling that allows us to progressively re-enable namespaces during storage infrastructure incidents. This will allow us to ensure that key dependencies, including Access and WARP, are able to come up without risking a denial-of-service against our own infrastructure as caches are repopulated.

This list is not exhaustive: our teams continue to revisit design decisions and assess the infrastructure changes we need to make in both the near (immediate) term and long term to mitigate the incidents like this going forward.

This was a serious outage, and we understand that organizations and institutions that are large and small depend on us to protect and/or run their websites, applications, zero trust and network infrastructure.  Again we are deeply sorry for the impact and are working diligently to improve our service resiliency. 



Source link

Xabi y Llopis avisan a Courtois, la norma que puede cambiarlo todo esta temporada

0


El Real Madrid está listo para competir en el Mundial de Clubes, ya que la entidad madridista llegó anoche a territorio norteamericano.

Los merengues comenzarán a trabajar desde este domingo con la plantilla al completo en el debut contra el Al-Hilal en el Hard Rock Stadium.

Sin embargo, el cuerpo técnico de Xabi Alonso ya está realizando algunas sesiones individuales con los futbolistas, algo que se ha demostrado con el trabajo que está haciendo Luis Llopis con Thibaut Courtois.

Cambio en la regla

El preparador de porteros le ha dejado claro al belga las novedades que quiere implementar el tolosarra, pero también le ha advertido de un cambio en el reglamento, algo que ha explicado muy bien Pierluigi Collina en el diario AS.

La IFAB busca acabar con la pérdida de los porteros, por lo que estos no deberán estar más de 8 segundos con el balón.

Pierluigi Collina

Es la novedad más importante, la que de verdad tiene como objetivo acabar con las pérdidas de tiempo. Será implementada en todas las competiciones del fútbol desde este verano. Ya fue usada en la Copa Libertadores y en la Sudamericana y funcionó muy bien. Si los porteros saben que se les pita córner en contra, no arriesgan. De hecho, en los primeros 160 partidos de Libertadores y Sudamericana sólo se aplicó la regla dos veces. Le aseguró que los porteros no van a tardar 15, 20 o 25 segundos en sacar. Esta es una buena noticia para le juego”, aseguró el mítico portero italiano.

Esta explicación de Pierluigi Collina confirma que Thibaut Courtois deberá tener mucho cuidado, especialmente porque el colectivo arbitral tiene la orden de ser muy severo con este cambio de la IFAB en la reglamentación, por lo que Luis Llopis ha sido muy claro con el belga.



Source link

‘I’m still here!’ Maria, 37, stuns Rybakina to reach Queen’s semis

0


Three years after her stunning run to the Wimbledon semifinals as a 34-year-old mother of two, Tatjana Maria is doing it again on grass.

Watched by husband Charles-Edouard and 11-year-old daughter Cecilia, the qualifier continued to slice and dice her way through the HSBC Championships draw with her biggest victory of the week, upsetting No. 4 seed Elena Rybakina 6-4, 7-6(4) in 1 hour and 45 minutes.

“I’m still here!” Maria said in her on-court interview. “And I’m living this dream with my family with me. … It’s a perfect example to never give up and always keep going.”

Keys edges Shnaider in three sets to reach Queen’s semifinals

The result is Maria’s second Top 20 victory at Queen’s this week, following her second-round defeat of Karolina Muchova — which was her first win over an opponent in that echelon since that 2022 Wimbledon showing. The 37-year-old advances to her first tour-level semifinal since Cleveland 2023, and her first above WTA 250 level since — you guessed it — Wimbledon 2022.

Maria will face another big hitter in the last four, No. 2 seed Madison Keys. The Australian Open champion navigated past No. 5 seed Diana Shnaider in a 2-6, 6-3, 6-4 clash of powerful strikes to reach her fourth semifinal of 2025, and first since Indian Wells in March. Keys leads the head-to-head against Maria 3-0, including a 6-4, 6-4 victory in their only previous grass-court meeting at Wimbledon 2015.

Slicing, dicing … and big serving: From the outset, Maria’s sliced groundstrokes off both wings, with their low, awkward bounces on the grass, proved effective at either keeping Rybakina off balance or drawing errors from the Kazakhstani. The German was quick to take advantage with brilliant net skills, nailing high backhand volleys as well as delicate crosscourt angles. When Rybakina did manage to get on the front foot, Maria still found a way to weave her web in defense, particularly with her touch on the lob.

“The grass fits for me perfectly, because it takes the slice really good and it keeps it low,” Maria told press afterward. “This is the hard part for players, because nobody plays like me.”

Maria also repeatedly outfoxed Rybakina by making counterintuitive shot choices that turned out to be strokes of genius. Up 4-3 in the second set, she had to hare across the court to track down a volley — but Rybakina was already moving to cover the open space down the line. Instead, Maria managed to caress the ball crosscourt, back to where Rybakina had been a second previously, to wrong-foot her opponent.

However, in important moments Maria was able to go back to basics. She saved 10 out of 12 break points against her, frequently with service winners or aces. She tallied nine of the latter, including two in the second-set tiebreak — just one behind Rybakina’s total of 10.

Rybakina threatened a comeback throughout the second set, going up 3-1 and then forcing a tiebreak from 5-3 down. But the stretches where she found her range were brief, and with the tiebreak balanced at 4-4 she committed a crucial double fault.

Keys’ insights into marital harmony: After a hard-fought, high-quality win that came down to a single break of serve in the third set, Keys was full of praise for Shnaider. But the on-court interviewer was also interested in her tactical approach — particularly when it came to following husband and coach Bjorn Fratangelo’s instructions. On a number of occasions, Fratangelo advised a serve down the T — but Keys responded by going wide.

“Sometimes I don’t like where he’s telling me to serve,” Keys said. “So I just take it as an option, and I choose to do something else. That’s why we work so well together!”

Keys also drew laughs from a slightly astonished crowd, on one of the hottest days of the British year so far — reaching a high of a balmy 27°C — by describing the weather as “a nice winter day,” from her Floridian perspective.



Source link