Connect with us

News

Wanindu Hasaranga, Shaheen Afridi and Azam Khan help Desert Vipers conquer Gulf Giants

Published

on

Spread the love

Shaheen Afridi’s deadly spell of three wickets for 22 runs and breezy knocks from Wanindu Hasaranga and Azam Khan guided Desert Vipers to a six-wicket win over defending champions Gulf Giants in the seventh match of the DP World ILT20 Season 2 at the Dubai International Stadium. The clash of the finalists of the first edition saw Afridi’s spell restrict Giants to 160 for 6 in 20 overs.

Vipers won the match with eight balls to spare through Hasaranga’s 42 off just 19 balls with four boundaries and two sixes. He had put on 57 runs in 33 deliveries for the third wicket with Adam Hose. Afzal Khan then hit a breezy unbeaten 26 off 14 balls with three boundaries and a six. He too added 41 runs in 19 balls for the fourth wicket with Hose, who hit a sedate 39 runs off 35 balls with four boundaries. Vipers who were at the bottom of the table have now jumped to the fourth place.

For the Giants, Chris Lynn top scored with 63 runs off 42 balls with seven boundaries and three sixes. He put on 89 runs off 59 balls for the third wicket with Jordan Cox before Afridi put the brakes on the run flow. Cox hit 32 off 29 balls with a boundary and a six.

Vipers won the toss and chose to bowl. In the opening over, Pakistan T20 skipper Afridi, making his tournament debut, conceded a boundary to Jamie Smith over mid-off off the fifth ball. Mohammad Amir took a wicket in the second over, dismissing skipper James Vince for 1 as he lifted the ball to Colin Munro at mid-on. Afridi also claimed a wicket in the third over, clean bowling Smith for 5 after a missed big hit.

Lynn wiped away the impact of two early wickets by scoring two boundaries and a six off Tymal Mills. Cox played second fiddle as Lynn went for the big hits. Lynn reached his half-century in 35 balls with six boundaries and three sixes. When the Giants were four runs short of the 100-run mark, Mills made Lynn miscue his shot, and wicketkeeper Azam Khan caught the skier for 63.

Shimron Hetmyer, who joined Cox, got out caught behind for 10 off Hasaranga. After that, Afridi picked his second wicket, forcing Cox to hit to Alex Hales at long-on for 32. Chris Jordan became Afridi’s third victim, falling identically for 14. Usman Khan hit an unbeaten 16 to ensure his team a challenging total.

Needing 161 to win, Vipers lost an early wicket when Richard Gleeson, who came in as Super Sub in place of Lynn, got Colin Munro out caught at third man for 6. Hales on 11 escaped being stumped off a Mujeeb Ur Rehman slider but fell in the seventh over to Dominic Drakes to a spectacular catch by Aayan Khan at the fine leg boundary for 21.

Hasaranga who joined Adam Hose hit Aayan Khan for two consecutive boundaries and also Jordan for a six and a boundary off successive balls. At the half way mark, Vipers needed 85 runs to win. Drakes picked the valuable wicket of Hasaranga in the 13th over by getting him caught by Usman Khan at long-off for 42.

Azam Khan unleased his hard-hitting skills and whacked Jordan for a six to mid-wicket followed by three boundaries off Blessing Muzarabani in the 15th over. This reduced the target to a gettable 32 runs from the last five overs. Hose got out to Gleeson, caught behind for 39 but Sherfane Rutherford and Khan steered their team to the target.

Vipers skipper Colin Munro hailed Hasaranga and Afridi; “It was a team effort, winning the toss was a big favour. Hasaranga was just brilliant, what a player. When you come up against Gulf Giants, we need to have our plans in place. We have all the analysts in T20 cricket, but what’s most important is adapt to what is in front of you. Afridi was outstanding and has so much experience, he knows his skill and executes them really well.”

Giants skipper Vince lauded Hasaranga’s knock. “We started well with the ball, put the pressure on them, but the way Hasaranga came out and batted took the game away from us. We need to tidy up in all facets on the game. We can’t afford to have lull periods because quality opposition will make you pay.”

Player of the match Hasaranga said: “I bat at number 7 generally, but today I had a chance up the order so I tried to go on the attack. I like to have that all-rounder tag in front of my name, so happy to perform with the bat as well.”

With 20 years of experience across print, TV, and digital journalism, Sudhashree is a seasoned media professional with a keen eye for news. A true news bug, she thrives on curating stories that capture the pulse of fashion, film, and all things trending. Deeply immersed in the fast-evolving media landscape, she swears by the power of social media to shape narratives and spark conversations.

Continue Reading
Advertisement

News

Five-day UAE National Day break: Residents to enjoy long weekend

Published

on

Spread the love

UAE residents can look forward to a five-day break for the country’s 55th National Day, with the government announcing a three-day paid holiday for employees in the public sector.

December 2, 3 and 4 have been declared public holidays for ministries and federal entities. Regular working hours will resume on Monday, December 7.

With Saturday and Sunday already forming the weekend for many employees, the announcement creates a five-day break for those following the standard two-day weekend.

Eid Al Etihad, as the National Day celebrations are officially known, traditionally falls on December 2 and 3. The addition of Friday, December 4, means public sector employees will not need to take annual leave to extend their holiday over the weekend.

How the UAE holiday transfer rule works

A law introduced in 2025 allows certain public holidays to be transferred to the beginning or end of the week when they fall mid-week. The measure is intended to create longer consecutive breaks for residents.

The rule was applied to last year’s National Day holiday. December 2 and 3, which fell on Tuesday and Wednesday, were moved to December 1 and 2, Monday and Tuesday, giving residents a four-day break when combined with the weekend.

Long weekends often provide an opportunity for residents to plan holidays, staycations, family gatherings or simply enjoy time off. The National Day break is among the major dates on the UAE’s annual holiday calendar, coinciding with the cooler winter season.

Celebrating with communities

Eid Al Etihad commemorates the unification of the seven emirates in 1971 and the formation of the United Arab Emirates. The country marks 55 years of the Union in 2026.

This year’s celebrations will place families, generations and communities at the centre, recognising the people and shared experiences that have shaped the UAE over the past 55 years. Eid Al Etihad will celebrate the nation as a “family of families”, highlighting the sense of belonging and unity among citizens and residents.

Continue Reading

News

UAE federal government employees to get five-day Eid Al Etihad break

Published

on

Spread the love

Federal staff will get three official public holidays from December 2 to 4, creating a five-day break when combined with the weekend

Federal government employees in the UAE will enjoy a five-day break in December after the government announced a three-day holiday to mark the country’s 55th Eid Al Etihad.

According to the UAE Government Media Office, the official holiday will run from Wednesday, December 2, to Friday, December 4, 2026.

With the holiday falling alongside the regular Saturday and Sunday weekend, federal government employees will have five consecutive days off. Official working hours will resume on Monday, December 7.

UAE marks 55 years of Eid Al Etihad

The holiday commemorates the UAE’s 55th Eid Al Etihad, marking the anniversary of the country’s formation on December 2, 1971.

The occasion is celebrated across the seven emirates with national events, cultural programmes, fireworks and community activities. It is an opportunity for residents to reflect on the country’s history, achievements and development since its founding.

The December break will give federal government employees an extended opportunity to take part in the celebrations and spend time with family and friends.

Continue Reading

News

What caused the global Microsoft outage and which services were affected?

Published

on

Spread the love

For millions of people who rely on Microsoft for work, Thursday’s disruption meant more than an application failing to load. Emails became difficult to access, workplace conversations were interrupted, and documents stored online were suddenly out of reach.

Microsoft’s widespread service outage, which began on November 12, continued into Friday, November 13, as the company struggled to restore normal operations across its Microsoft 365 ecosystem. Outlook, Teams, Word, Excel and PowerPoint were among the services affected, alongside business platforms such as SharePoint and OneDrive.

The disruption lasted for more than five hours during its initial phase, but the problems did not end when the first signs of recovery emerged. Thousands of users were still reporting difficulties nearly 24 hours later, suggesting that the company was dealing with a more complicated infrastructure problem than a temporary application failure.

Microsoft said the incident stemmed from unexpected server failures that put additional pressure on the systems still operating. It ruled out a sudden surge in user traffic and said there was no indication that a cyberattack was responsible.

From email problems to disrupted workplaces: What stopped working?

The outage spread across several services that individuals and organisations use to manage their daily work.

Outlook was among the most affected platforms, with users reporting trouble opening inboxes, sending and receiving messages, and connecting to Exchange Online mailboxes. Teams users also encountered connection problems, affecting access to the communication and video-conferencing platform.

The disruption extended beyond email and meetings. Users also reported problems with Word, Excel and PowerPoint, while SharePoint Online and OneDrive were affected, making it harder to reach shared documents and cloud-stored files.

The list of potentially affected services included Microsoft’s AI assistant, 365 Copilot, as well as Microsoft Defender XDR, Planner, To Do, Intune and Defender for Office 365.

Some Microsoft Purview capabilities were also disrupted. These included functions linked to authorisation, data classification, automatic labelling, data loss prevention and communication compliance.

The impact was not restricted to one part of the world. Microsoft warned that customers in different regions could experience problems, turning the incident into a wider disruption for businesses and individual users.

Why did the Microsoft outage happen?

The scale of the disruption raised an obvious question: why were so many services affected at the same time?

Microsoft’s explanation pointed to a failure within its server infrastructure. Although the company initially referred to elevated loads, it later clarified that an increase in user traffic was not behind the problem.

Instead, several servers had unexpectedly become unavailable. That left the remaining infrastructure carrying additional workloads, increasing pressure on systems that were still functioning.

The company also identified failures involving automated server health checks. These checks are designed to monitor server performance and determine whether individual systems are operating properly. Problems with the monitoring process contributed to affected servers being marked as unavailable.

Microsoft began investigating whether a particular component involved in processing these checks was contributing to the failures. Engineers tested a configuration change on a portion of the affected infrastructure to see whether it could help restore server availability.

The company also paused deployments and took steps to prevent additional servers from being removed from service.

Importantly, Microsoft said its investigation had found no indication of a cyberattack. The explanation it provided centred on server availability and the systems responsible for monitoring infrastructure health.

Microsoft’s recovery effort: Moving traffic and restarting servers

With services affected across its network, Microsoft’s immediate priority was to reduce pressure on the infrastructure that remained operational.

The company began redirecting additional connection traffic away from affected systems and distributing it across other parts of its global network. It also started restarting affected servers in an effort to bring them back online.

In a further step, Microsoft tested an alternative method for carrying out server health checks. The company said this approach helped return some affected servers to service and that it planned to apply the change more widely.

It was also preparing automated recovery systems to identify unresponsive servers and restart them, with the aim of making the restoration process more effective.

There were signs of improvement on Thursday evening. By around 6pm ET on November 12, Microsoft reported limited recovery, with some users gradually reconnecting to its services.

Figures cited by Reuters showed that complaints on Downdetector had also begun to fall. Outlook-related reports dropped from a peak of 138,058 around 1pm ET to approximately 34,490 by the evening. Reports concerning Microsoft 365 had declined to nearly 13,000 by 5:47pm ET.

But falling complaint numbers did not mean the disruption was over. Microsoft cautioned that users would experience a gradual return to normal as server capacity came back and applications reconnected.

When will Outlook and Microsoft 365 be fully restored?

By Friday, November 13, the recovery was still a work in progress. Users continued to report difficulties logging in, opening Outlook inboxes and connecting to Microsoft 365 applications.

Microsoft had not provided a definitive timeline for the complete restoration of every affected service in the updates covered here.

For businesses that depend on Microsoft’s cloud-based tools, the prolonged disruption highlighted how closely everyday operations are tied to access to email, shared files and online collaboration platforms.

The company was continuing to bring affected servers back into service and reduce the pressure on its remaining infrastructure. Until that process was complete, some users could continue to experience intermittent access problems.

(With inputs from agencies)

Continue Reading

Popular

© Copyright 2025 HEADLINE. All rights reserved

https://headline.ae/