Get a notification when your tools are down!

IsDown makes it easy to monitor all your business tools status from one place.

Sign up with Google or with email

Ongoing [Informative] Problem in creating media message template by Portal blip

Below is information about the reported failure, regarding the disapproval of WhatsApp's media message template when submitted by the blip Portal, with ...


3 incidents in the last 7 days

4 incidents in the last 30 days

Automatic Checks

Last check: less than a minute ago

Last known issue: 18 days ago

Latest Incidents

Last 30 days


Resolved Blank Ticket history

We identified in our monitoring an issue related to viewing ticket history.

about 13 hours ago Official incident report

Resolved Portal and Desk degradation

We identified in Monitoring, a degradation (or instability) of the platform

Resolved Broadcast Plugin

We are currently unavailable to send a broadcast by the Portal Plugin. Our team is already working on it and we will give an update soon.

Resolved WhatsApp Button template failure - Facebook

We identified a flaw in the button template in WhatsApp. impact for the customer: For customers who use this button template feature in the flow of smart contact (Bot). Action in progress: In the analysis carried out by the technical team at Take Blip, no evidence of failure in our environment was identified to justify the observed scenario. With the fault logs collected at the WhatsApp Gateway, we triggered our partner Facebook during the night. We are dealing with the card directly with Facebook. We escalated the ticket and we are waiting for the return from Facebook. Follow the link to the Facebook status page (

about 1 month ago Official incident report

Resolved BLiP Outage

We are experiencing an unavailability on our platform. Impact: The smart contacts are unavailable and are not responding in all channels. Our team is already working and we will soon update.

about 1 month ago Official incident report

Resolved Permission failure and login limitation - Facebook

We have identified a failure in the active message triggering model on the Blip Portal. Impact: Failure in the creation and visualization of the firing template within the Blip portal. Action: Our technical team has already identified the fault and are working to correct the failure.

about 1 month ago Official incident report

Resolved Desk Application Degradation

In our monitoring, we identified a degradation in the Desk. The team is already verifying this degradation.

about 1 month ago Official incident report

Resolved [Informative] - Problem in the variables of the custom reply in the Desk service tool

Status Update: Due to an update carried out in the scheduled maintenance window (carried out on April 28, 2020 at around 11: 30 pm) in the Desk application, we had problems when returning the value contained in the variables used in the “Custom reply” ​​within the screen service desk. Impact: In the Desk attendant screen, when using the “custom reply” feature that uses a variable in the text, only the name of the field is returned and not the value of the variable. It is worth mentioning that the impact is low since only one resource is not being filled in automatically, and can be filled in manually. Correction action: Given that the identified failure is due to an update in production Rollback mapping as a solution action. For this specific scenario, the maneuver involves a restart in the Desk Application service. This action may cause an even greater impact if performed during business hours, since disconnection and subsequent connection of all the attendants who are logged in occurs, so it was defined that the rollback will be performed within the maintenance window on today's date (29/04/2021) at 10 pm.

about 2 months ago Official incident report

Resolved Degradation Partial

Through our monitoring, we identified a degradation in our platform, causing several slowdowns in usability. Our technical team is already analyzing what is causing the impact of the failure to the customer: Slow platform usability. The failure is intermittent.

about 2 months ago Official incident report

How it works?

  1. Step 1 Create an account

    Start with a free account that will allow you to monitor up to five services. Sign up via Google, Slack, or email.

  2. Step 2 Select your tools

    There are 1000 services to choose from, and we're adding more every week.

  3. Step 3 Set up notifications

    You can get notifications through the mail, Slack or use Zapier or Webhooks to build your workflows.

  4. Step 4 You're ready!

    You'll never be caught by surprise again. Every time there's a problem with one tool, you'll get a notification ASAP.

Don't be the last to know!

We're monitoring 1000 services and adding more every week.

All-in-one platform to check the status of all your cloud services

IsDown integrates with hundreds of services. Handles the hassle of going to each one of the status pages and manage it one by one. We also help control how you receive the notifications.
We monitor all problems and outages and keep you posted on their current status in almost real-time.

Get notifications in your favorite communication channel

You can easily get notifications in your email, slack, or use Webhooks and Zapier to introduce the service status in your workflows.



Empower your teams with more data

IsDown collects the status from services to help you be ahead of the game.


You already monitor internal systems. Add another dimension (external systems) to your monitoring data and complement it with the external factors.

Customer Support

Know before your clients tell you. Anticipate possible issues and make the necessary arrangements.


One of your competitors is down? Maybe a good time to spread the word about your service.

Trusted by teams from all over the world

Services Available
Incidents registered
Monitoring Incidents

Ready to dive in? Start using IsDown today.

Sign up for free