Incidents reported on status page for Zernio https://www.zernio-status.com/ https://d1lppblt9t2x15.cloudfront.net/logos/b2b26fe9a73f78b21d614900665ecd03.png https://www.zernio-status.com/ en https://www.zernio-status.com/ Tue, 12 May 2026 13:21:15 +0000 https://www.zernio-status.com/#a4642703e25d7e33eb31236093aadf20524b7e89274fea010020ff75309388d2 Queue Scheduler recovered https://www.zernio-status.com/ Tue, 12 May 2026 13:07:40 +0000 https://www.zernio-status.com/#a4642703e25d7e33eb31236093aadf20524b7e89274fea010020ff75309388d2 Queue Scheduler went down https://www.zernio-status.com/ Tue, 12 May 2026 09:04:00 +0000 https://www.zernio-status.com/#0ba5288e8756998bf9c2eef904dbb92fda3dc6bed77345cbba1f187e0e74f53c Queue Scheduler recovered https://www.zernio-status.com/ Tue, 12 May 2026 07:07:36 +0000 https://www.zernio-status.com/#0ba5288e8756998bf9c2eef904dbb92fda3dc6bed77345cbba1f187e0e74f53c Queue Scheduler went down https://www.zernio-status.com/incident/880964 Sat, 02 May 2026 12:06:00 -0000 https://www.zernio-status.com/incident/880964#c67ac8533a239ca330db34c8f7666e710ddee8d21faf84e91d0c3019b1689d1d Meta platform incident: Instagram, Threads, and Facebook publishing failures We're investigating a Meta-side issue causing posts to fail across Instagram, Threads, and Facebook. This is NOT specific to Zernio, other major schedulers are reporting the same incident. Meta's Graph API is intermittently failing to fetch media even when URLs are publicly accessible. Error codes: 9004 / 2207052 (images), 9004 / 2207076 (videos). We're monitoring the situation closely and we'll keep you posted as it evolves. What you can do - Don't bulk-retry and don't reconnect your account. Neither helps while Meta is unstable. We'll update as it evolves. Not on us this time, still our problem. Sorry for the disruption. https://www.zernio-status.com/incident/880964 Mon, 27 Apr 2026 13:21:00 -0000 https://www.zernio-status.com/incident/880964#d4827e8801c64852bf288e2d80c9871576fd2d50eb8bf7dfd90fae06fce2aadb Instagram Graph API is intermittently failing to fetch media when we send a post for publishing, even when the media URL is public and returns HTTP 200 from everywhere else. The error surfaces in your dashboard as "Media fetch failed, retrying..." and the post ends up in failed after our 4 retry attempts. Meta's underlying error code is 9004 / subcode 2207052 (images) and 2207076 (video). This is being widely reported by other developers in Meta's community thread, with reports starting April 2 and waves recurring through April 27. No official statement from Meta yet. What we're doing Not auto-retrying inside the storm. We cap at 4 attempts to avoid burning your Instagram rate limit while Meta is unstable. Monitoring globally. Once the error rate drops below 20/hour for an hour and customer hosts stay clean for 2 hours, we auto-requeue the posts that failed during the window. You won't have to retry one-by-one. Tracking the Meta thread for any official update. What you can do Don't bulk-retry. Manual single retries sometimes work on the 2nd or 3rd try, mass retries just waste your IG limit. Don't reconnect your IG account. Tested, doesn't change anything. Don't switch CDN. Reports show every host is affected equally. TikTok, X, LinkedIn, YouTube, Facebook, Threads are unaffected. If you want us to confirm whether specific failed posts match this incident, reply with the post IDs and we'll check. We'll update this post as it evolves. Not on us this time, still our problem https://www.zernio-status.com/incident/880243 Fri, 24 Apr 2026 17:44:00 -0000 https://www.zernio-status.com/incident/880243#a56e297fa15d01dbb6589dc931b4eb1c479011a92a677074a73ccb5d426cb257 We are currently experiencing an issue affecting the ability to reply to comments on Instagram through our platform. After investigation, we have confirmed that this behavior is caused by a bug on Meta/Instagram’s side, and is not originating from our systems. What’s happening: Replies to existing comments on Instagram posts may fail or not be published correctly. What is working as expected: Creating top-level comments (POST /v1/inbox/comments/{postId} without a commentId) continues to work normally. Sending DMs to commenters via /private-reply is functioning correctly. Comment automations are still successfully sending the DM portion. What we’re doing: We have verified the root cause and reported the issue to Meta. We are actively monitoring the situation and will provide updates as soon as more information becomes available. What you can do: At this time, there is no workaround within our platform for replying to comments. If urgent, replies may need to be posted directly through the Instagram app. We understand how important this functionality is and will keep you informed of any progress or resolution. https://www.zernio-status.com/ Wed, 15 Apr 2026 10:21:31 +0000 https://www.zernio-status.com/#348dc151c0c40da3933e1412ae963ecc50ec9fe51847dd355744f8d8fe06aee2 Queue Scheduler recovered https://www.zernio-status.com/ Wed, 15 Apr 2026 10:17:24 +0000 https://www.zernio-status.com/#348dc151c0c40da3933e1412ae963ecc50ec9fe51847dd355744f8d8fe06aee2 Queue Scheduler went down https://www.zernio-status.com/ Wed, 15 Apr 2026 01:11:26 +0000 https://www.zernio-status.com/#cc3349d3ebb0d272b8ed82ffcc0362f7de47710d25c848d8553e2c26089ba7d4 Queue Scheduler recovered https://www.zernio-status.com/ Wed, 15 Apr 2026 01:07:18 +0000 https://www.zernio-status.com/#cc3349d3ebb0d272b8ed82ffcc0362f7de47710d25c848d8553e2c26089ba7d4 Queue Scheduler went down https://www.zernio-status.com/ Tue, 14 Apr 2026 22:30:31 +0000 https://www.zernio-status.com/#e58512f54d72e1bc5d347041f9ca14d08c98ef52169ecb839f06c5fe77cfba60 Queue Scheduler recovered https://www.zernio-status.com/ Tue, 14 Apr 2026 22:22:20 +0000 https://www.zernio-status.com/#e58512f54d72e1bc5d347041f9ca14d08c98ef52169ecb839f06c5fe77cfba60 Queue Scheduler went down https://www.zernio-status.com/ Tue, 14 Apr 2026 20:13:22 +0000 https://www.zernio-status.com/#08161ed7af7a94622544ca5ebff2789b8201da55e0fb63db581d35fea13f6a75 Queue Scheduler recovered https://www.zernio-status.com/ Tue, 14 Apr 2026 20:08:19 +0000 https://www.zernio-status.com/#08161ed7af7a94622544ca5ebff2789b8201da55e0fb63db581d35fea13f6a75 Queue Scheduler went down https://www.zernio-status.com/ Tue, 14 Apr 2026 14:33:38 +0000 https://www.zernio-status.com/#7bf086d49c80f84c0e7f114f12805b4a02776ba5c97731e784e36a28f292d5fd Queue Scheduler recovered https://www.zernio-status.com/ Tue, 14 Apr 2026 14:28:28 +0000 https://www.zernio-status.com/#7bf086d49c80f84c0e7f114f12805b4a02776ba5c97731e784e36a28f292d5fd Queue Scheduler went down https://www.zernio-status.com/ Tue, 14 Apr 2026 10:11:19 +0000 https://www.zernio-status.com/#53d925a49ec2cc6cb06a1d349ca7d474971f468b29598d491fc3ddd04f1ae281 Queue Scheduler recovered https://www.zernio-status.com/ Tue, 14 Apr 2026 10:07:17 +0000 https://www.zernio-status.com/#53d925a49ec2cc6cb06a1d349ca7d474971f468b29598d491fc3ddd04f1ae281 Queue Scheduler went down https://www.zernio-status.com/ Mon, 13 Apr 2026 22:14:37 +0000 https://www.zernio-status.com/#e1bed52e77bdce34abbf0bfdf8c8807ef8e44b9ebd2dfbaa9f876aa14877b44d Queue Scheduler recovered https://www.zernio-status.com/ Mon, 13 Apr 2026 22:07:41 +0000 https://www.zernio-status.com/#e1bed52e77bdce34abbf0bfdf8c8807ef8e44b9ebd2dfbaa9f876aa14877b44d Queue Scheduler went down https://www.zernio-status.com/ Mon, 13 Apr 2026 20:28:33 +0000 https://www.zernio-status.com/#56be18cb200c0b6f7f96687d9886166fd6893cabb35946b2bb6ab876c9185f88 Queue Scheduler recovered https://www.zernio-status.com/ Mon, 13 Apr 2026 20:27:40 +0000 https://www.zernio-status.com/#56be18cb200c0b6f7f96687d9886166fd6893cabb35946b2bb6ab876c9185f88 Queue Scheduler went down https://www.zernio-status.com/ Mon, 13 Apr 2026 17:19:33 +0000 https://www.zernio-status.com/#1cca06a662ced503947f333385a2c29536761279e41d9f278a9d672cf5674dde Queue Scheduler recovered https://www.zernio-status.com/ Mon, 13 Apr 2026 17:17:18 +0000 https://www.zernio-status.com/#1cca06a662ced503947f333385a2c29536761279e41d9f278a9d672cf5674dde Queue Scheduler went down https://www.zernio-status.com/incident/858458 Fri, 27 Mar 2026 07:34:00 -0000 https://www.zernio-status.com/incident/858458#385b3e662a1506f55f78401283e9904b4d0122df80478b7ea7dbf8155fde80ac We’re back! TikTok publishing should be up and running. Thanks for bearing with us. https://www.zernio-status.com/incident/858458 Wed, 25 Mar 2026 20:39:00 -0000 https://www.zernio-status.com/incident/858458#5b4434bc8568ffedc989743ea8a1c375eac4bfdcbede353573a897f5df45155d We are currently experiencing an issue affecting TikTok publishing from Zernio. Some posts are failing during the upload process and are not appearing on TikTok. This is caused by an ongoing issue with TikTok’s API, which is impacting the delivery of certain posts. Our team is aware of the situation and is closely monitoring it while awaiting a resolution from TikTok. https://www.zernio-status.com/ Sun, 15 Mar 2026 17:45:18 +0000 https://www.zernio-status.com/#5a8ea449f07875734697730648f42cfb857c8e81b8d8422df58d1a63135bdb82 Queue Scheduler recovered https://www.zernio-status.com/ Sun, 15 Mar 2026 17:37:30 +0000 https://www.zernio-status.com/#5a8ea449f07875734697730648f42cfb857c8e81b8d8422df58d1a63135bdb82 Queue Scheduler went down https://www.zernio-status.com/ Fri, 06 Mar 2026 10:16:37 +0000 https://www.zernio-status.com/#6275720d6d6e32222d35537c537cf371e8fcea09b5bb4952fc3e1f1bd4c27290 Queue Scheduler recovered https://www.zernio-status.com/ Fri, 06 Mar 2026 10:01:35 +0000 https://www.zernio-status.com/#6275720d6d6e32222d35537c537cf371e8fcea09b5bb4952fc3e1f1bd4c27290 Queue Scheduler went down