Teamleader
Identified - LinkedIn is putting a new version in place which causes our Chrome Extension to break.
We are working on an update of the Chrome Extension to resolve the issue.
Not all LinkedIn accounts are updated at once, so for the old version, everything still works.
Dec 21, 17:38 CET
Teamleader Operational
External Services ? Operational
Email ? Operational
Cloudsign ? Operational
Cloudproject ? Operational
API Operational
Webhooks Operational
Voip (Twilio) Operational
Chrome Extension Partial Outage
Document Processing Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Web Uptime
Fetching
Web Response Time ?
Fetching
Past Incidents
Jan 18, 2017
Resolved - All issues concerning document creation have been resolved. If you have any further questions or if you experience difficulties, please contact support@teamleader.eu.
Jan 18, 09:55 CET
Monitoring - The problems have been resolved. We're monitoring the situation but feel free to start generating documents again.
Jan 17, 15:59 CET
Identified - There are still some minor issues with template fonts. We're following up and will get back to you soon.
Jan 17, 10:24 CET
Jan 16, 2017
Resolved - Fonts are properly included again. - All document generation is hence operational again.

Some customers might have generated empty documents or documents with different fonts.
We are currently in progress of regenerating these documents.
In case necessary, we will communicate about this to the customers involved.
Jan 16, 20:41 CET
Update - We verified that the document generation works again.
There are issues with some of the fonts in the PDFs, further investigation is going on.
Jan 16, 16:59 CET
Monitoring - We deployed a new version of the document server.
It will handle document generation properly again.
We'll keep a close eye to its behavior.
Jan 16, 16:21 CET
Identified - We're one step closer to a solution. Working on a fix right now.
Back with more news soon.
Jan 16, 15:53 CET
Update - We're still researching the problem and working hard on a solution.
Jan 16, 15:32 CET
Investigating - Our service that is processing documents is having problems. We're investigating the issue.
Jan 16, 14:44 CET
Resolved - This incident has been resolved.
Jan 16, 10:06 CET
Monitoring - We fixed the DNS issue by moving towards a complete new subdomain, to force invalidate caches.
We are now monitoring to see if all users can login again.
Jan 16, 09:53 CET
Identified - After a successful migration towards new servers during the night, we now experience login issues.
These are caused by cached DNS-records and don't affect everyone.
We are actively working on a solution.
Hold tight for a better Teamleader experience, coming up very soon!
Our apologies for the delay.
Jan 16, 09:39 CET
Completed - We have successfully moved environment, we'll keep on monitoring Teamleader to fix any issues.
Jan 16, 02:55 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 15, 23:53 CET
Scheduled - We're moving Teamleader to a newer, faster environment. 3 hours of downtime and a faster Teamleader future ahead!
Jan 15, 23:13 CET
Jan 14, 2017

No incidents reported.

Jan 13, 2017

No incidents reported.

Jan 12, 2017
Resolved - This incident has been resolved.
Jan 12, 15:00 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 12, 10:12 CET
Identified - Due to a problem with our servers, our system isn't able to handle any requests. We've identified the issues and are resolving them as quickly as possible.
Jan 12, 10:04 CET
Jan 11, 2017

No incidents reported.

Jan 10, 2017

No incidents reported.

Jan 9, 2017
Resolved - This incident has been resolved.
Jan 9, 19:11 CET
Identified - We've identified the issue and stabilized the application.We'll be further investigating the issue
Jan 9, 16:16 CET
Investigating - We experience an extraordinary load which is causing server failure.
We are investigating the issue.
Jan 9, 15:58 CET
Jan 8, 2017

No incidents reported.

Jan 7, 2017

No incidents reported.

Jan 6, 2017

No incidents reported.

Jan 5, 2017

No incidents reported.

Jan 4, 2017

No incidents reported.