budice0 retweeted
A new holiday tradition set at the most magical place on Earth.
Hallmark’s Holiday Ever After: A Disney World Wish Come True streams on Disney+ and Hulu beginning November 29.
budice0 retweeted
Starbucks Red Cup Day is TOMORROW (Tuesday the 17th) and here's everything you need to know to score one before they run out!
The deal starts on November 17th at store open and you can get a FREE Red Cup with purchase of any holiday drink - this can be in-store, at the drive-thru, or even delivery orders.
Qualifying drinks include: Apple Pomegranate Refresher, Caramel Brulée Chai, Caramel Brulée Latte, Gingerbread Chai, Gingerbread Latte, Hot Chocolate, Iced Pumpkin Cream Chai, Peppermint Hot Chocolate, Peppermint Mocha, Pecan Crunch Oatmilk Latte, Pecan Oatmilk Cortado, Pumpkin Cream Cold Brew, Pumpkin Spice Latte, Snowy Apple Drink, Sugar Cookie Latte, Sugar Cookie Matcha, Tiramisu Velvet Cold Brew, Tiramisu Velvet Latte, White Hot Chocolate, Holiday and Fall Cold Foams and Protein Cold Foams.
Are you grabbing a Red Cup from @Starbucks tomorrow?
#starbucks #redcup #redcupday #strabuckscoffee #starbuckscups
budice0 retweeted
The news of Robert Pattinson as James Bond has been placed on a major billboard in London.
budice0 retweeted
Nicholas Hoult gotta be feeling like the Antonio Salieri to Robert Pattinson's Mozart
budice0 retweeted
“You’re impossibly fast and strong. You drive an Aston Martin. You drink martinis shaken and not stirred. You have a license to kill, and an astronomical body count in both meanings of the term. I know what you are…”
“Say it. Out loud. Say it!”
“Bond, James Bond”
budice0 retweeted
The Ian Fleming Estate and Ian Fleming Publications are delighted to welcome Robert Pattinson to the James Bond family.
As Bond himself reflects at the end of Moonraker when facing the fact that the object of his affections is engaged to another man, 'He must play the role which she expected of him. The tough man of the world. The Secret Agent. The man who was only a silhouette.' We look forward to Pattinson stepping into that silhouette and making it his own. We have no doubt that Ian Fleming would be amazed at the longevity of his creation and the fact that the world is still hungry for tales of the world’s greatest spy.
As the custodians of Ian Fleming's literary work, we wish Pattinson and everyone associated with the film the very best of luck. And as die-hard fans, we can’t wait for Bond 26.
budice0 retweeted
Sources tell The Hollywood Reporter that the process was so secretive that Pattinson was only informed he got the role Sunday morning, by Villeneuve himself. Pascal is said to have called the runner ups.
BREAKING: ROBERT PATTINSON IS JAMES BOND hollywoodreporter.com/movies…
budice0 retweeted
BREAKING: ROBERT PATTINSON IS JAMES BOND hollywoodreporter.com/movies…
budice0 retweeted
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
Replying to @MSFT365Status
We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.
budice0 retweeted
From the November 12 special screening of THE FURTHER MIS-ADVENTURES OF CLIFF BOOTH in Los Angeles moderated by Jonathan Groff with David Fincher, Elizabeth Debicki, Peter Weller and Kirk Baxter, with Steven Zaillian, Zach Cregger, Kelvin Harrison Jr. and more in attendance.
budice0 retweeted
Our gallery has been updated with the first HQ photos of Lily James attending the 17th Governors Awards in Los Angeles.
Check them out: lilyjamesphotos.com/thumbnai…







































