Deprecated: Return type of Aventura\Wprss\Core\DataObject::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/DataObject.php on line 783

Deprecated: Return type of Aventura\Wprss\Core\DataObject::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/DataObject.php on line 808

Deprecated: Return type of Aventura\Wprss\Core\DataObject::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/DataObject.php on line 770

Deprecated: Return type of Aventura\Wprss\Core\DataObject::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/includes/Aventura/Wprss/Core/DataObject.php on line 795

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 44

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 24

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 60

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 76

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 44

Deprecated: Return type of RebelCode\Wpra\Core\Entities\Collections\WpEntityCollection::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Entities/Collections/WpEntityCollection.php on line 97

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 60

Deprecated: Return type of RebelCode\Wpra\Core\Data\AbstractDataSet::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/src/Data/AbstractDataSet.php on line 76

Deprecated: Return type of Twig\Node\Node::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/vendor/twig/twig/src/Node/Node.php on line 213

Deprecated: Return type of Twig\Node\Node::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/techtvne/public_html/wp-content/plugins/wp-rss-aggregator/vendor/twig/twig/src/Node/Node.php on line 221
WhatsApp Receives 66,000 Reports as App Experienced Downtime | TechTV Network. Nigeria’s No 1 Digital Technology and Business Analysis Broadcast Platform - By
Menu Close

WhatsApp Receives 66,000 Reports as App Experienced Downtime

WhatsApp, the popular messaging platform went down earlier today and almost sent over two billion users across the globe into confusion as they could not reach their contacts.

The outage which lasted a little over two hours saw over 66,000 users make reports on the app downtime detector website – Downdetector.

The website reported that WhatsApp users started launching reports a few minutes before 8:00 AM on Tuesday and that by 8:30 AM, over 12,000 users had dropped downtime reports.

More checks on the website further revealed that the first reports started coming in at about 7:42 AM and continued till about 9:57 AM. Within this period, 66,241 reports had been made with the peak at about 8:42 AM.

On the issues reported, 56 percent of users reported an issue with sending messages on the app, 39 percent reported an issue with server connection and five percent launched a general report with the app.

The variation on the report comes amid the confusion by users on the main issue that prompted the shutdown.

Comments on Twitter revealed some users were completely unaware of the main cause of the downtime as most tried restarting their phones while some others thought they had issues with their Internet connections.

While commenting on the issue, a WhatsApp spokesperson confirmed the outage and also mentioned that the company was working to “restore WhatsApp for everyone as quickly as possible.”

With about two billion users worldwide, WhatsApp has failed to create a dedicated official avenue to update users on its outages.

Checks on its Twitter handle show that the last documented update on an outage was in 2014 which is incidentally, the last post made by the messaging platform on its Twitter handle.

Leave a Reply

Your email address will not be published. Required fields are marked *