Emergency Database Service Maintenance in IN-MUM

What to do

• Check whether you use Hostinger IN-MUM Shared servers (Mumbai, IN), IN-MUM Cloud servers (Mumbai, IN) in apac. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 38m it lasted.

  Anything that failed between 2026-06-03 10:33 UTC and 2026-06-03 14:10 UTC may need a replay.

• Subscribe to Hostinger's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=hostinger works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Hostinger 2

1. investigatingJun 3, 2026, 10:33 AM UTC

   We are investigating database connectivity issues in IN-MUM. Client websites hosted there could be temporarily inaccessible or might load slower than usual. There might be some recent entries lost in the database that were caused by database service anomalies. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.

   provider

2. resolvedJun 3, 2026, 2:10 PM UTC

   This incident is now closed. The intermittent database connection errors reported earlier were related to a new server-side protection. Affected customers can follow the steps in our support article (https://www.hostinger.com/support/how-to-fix-mysql-operation-not-permitted-error/) to apply the workaround, or contact our Customer Success team for help. We apologize for any inconvenience caused.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.