Many Vodafone users logged on to the popular Whirlpool forum to complain and about 10am yesterday a Vodafone spokesman posted a message saying that the issue was caused by a "known outage" but was now fixed.
The problem had not been fixed, however, and customers reported experiencing issues all throughout the day.
"Just spoke to vodafone – they say it's because of daylight saving and has been an issue for all other carriers calling vodafone since 2 am," one Whirlpool user wrote later in the afternoon.
At about 7:40pm last night, a Vodafone spokeswoman in a post on Whirlpool said the issue - which had finally been resolved - affected only calls between Telstra and Vodafone.
"The cause has been identified and our tech team have confirmed this issue has now been resolved and traffic is now moving between carriers," Vodafone wrote.
"I understand this issue may have been a major disruption to our customer's Sunday, and we apologise for any inconvenience caused."
Vodafone Australia did not respond to a request for comment at the time of writing.
Yesterday's glitch could not come at a worse time for the telco, which was forced to issue a blanket apology to customers in February over prolonged network issues. It also recently gave free calls to prepaid customers after a glitch prevented them from recharging their credit.
Meanwhile, the jury is still out on whether Apple has fixed the daylight saving bug that has plagued iPhone users around the world for several years. Users have consistently reported being woken up by their alarms either late or early or not at all due to glitches in switching to and from daylight saving time.
This time around, it appears some Australian iPhone users were hit with the bug while others escaped without issues. Users in Britain and the US reported experiencing the same bug earlier this year.
Apple could not clarify why the issue kept recurring but said customers should check their settings to ensure they had set their clock to update automatically and also ensure they had the latest software updates installed on their iPhones.
The daylight saving bugs come on top of a glitch earlier this year that meant thousands of iPhone owners were not awoken by their alarms on New Year's Day.
Fairfax reader Reuben Aitchison was woken up by his iPhone 4 at 6am this morning despite having his alarm set to 7am.
"For some reason, despite correctly switching from Daylight Saving Time to normal time yesterday morning, my trusty iPhone this morning decided that, no, it hadn't had enough of daylight saving, and it switched back," Aitchison wrote.
Sign up for Computerworld eNewsletters.