SuperCompany incident

Site Unreachable

Minor Resolved View vendor source →

SuperCompany experienced a minor incident on February 1, 2026 affecting inTeam API, lasting 10h 13m. The incident has been resolved; the full update timeline is below.

Started
Feb 01, 2026, 06:12 AM UTC
Resolved
Feb 01, 2026, 04:25 PM UTC
Duration
10h 13m
Detected by Pingoru
Feb 01, 2026, 06:12 AM UTC

Affected components

inTeam API

Update timeline

  1. investigating Feb 01, 2026, 06:12 AM UTC

    Issue opened on monitor failure.

  2. resolved Feb 01, 2026, 06:13 AM UTC

    Issue resolved on monitor recovery.

  3. investigating Feb 01, 2026, 06:28 AM UTC

    Issue re-opened on monitor failure.

  4. resolved Feb 01, 2026, 06:48 AM UTC

    Issue resolved on monitor recovery.

  5. investigating Feb 01, 2026, 06:51 AM UTC

    Issue re-opened on monitor failure.

  6. resolved Feb 01, 2026, 06:59 AM UTC

    Issue resolved on monitor recovery.

  7. investigating Feb 01, 2026, 07:02 AM UTC

    Issue re-opened on monitor failure.

  8. resolved Feb 01, 2026, 07:17 AM UTC

    Issue resolved on monitor recovery.

  9. investigating Feb 01, 2026, 07:24 AM UTC

    Issue re-opened on monitor failure.

  10. resolved Feb 01, 2026, 07:29 AM UTC

    Issue resolved on monitor recovery.

  11. investigating Feb 01, 2026, 07:36 AM UTC

    Issue re-opened on monitor failure.

  12. resolved Feb 01, 2026, 07:46 AM UTC

    Issue resolved on monitor recovery.

  13. investigating Feb 01, 2026, 07:49 AM UTC

    Issue re-opened on monitor failure.

  14. resolved Feb 01, 2026, 08:05 AM UTC

    Issue resolved on monitor recovery.

  15. investigating Feb 01, 2026, 08:15 AM UTC

    Issue re-opened on monitor failure.

  16. resolved Feb 01, 2026, 08:22 AM UTC

    Issue resolved on monitor recovery.

  17. investigating Feb 01, 2026, 08:41 AM UTC

    Issue re-opened on monitor failure.

  18. resolved Feb 01, 2026, 08:43 AM UTC

    Issue resolved on monitor recovery.

  19. investigating Feb 01, 2026, 08:49 AM UTC

    Issue re-opened on monitor failure.

  20. resolved Feb 01, 2026, 08:53 AM UTC

    Issue resolved on monitor recovery.

  21. investigating Feb 01, 2026, 08:59 AM UTC

    Issue re-opened on monitor failure.

  22. resolved Feb 01, 2026, 09:16 AM UTC

    Issue resolved on monitor recovery.

  23. investigating Feb 01, 2026, 09:26 AM UTC

    Issue re-opened on monitor failure.

  24. resolved Feb 01, 2026, 09:40 AM UTC

    Issue resolved on monitor recovery.

  25. investigating Feb 01, 2026, 09:42 AM UTC

    Issue re-opened on monitor failure.

  26. resolved Feb 01, 2026, 09:43 AM UTC

    Issue resolved on monitor recovery.

  27. investigating Feb 01, 2026, 09:48 AM UTC

    Issue re-opened on monitor failure.

  28. resolved Feb 01, 2026, 09:59 AM UTC

    Issue resolved on monitor recovery.

  29. investigating Feb 01, 2026, 10:09 AM UTC

    Issue re-opened on monitor failure.

  30. resolved Feb 01, 2026, 10:35 AM UTC

    Issue resolved on monitor recovery.

  31. investigating Feb 01, 2026, 10:54 AM UTC

    Issue re-opened on monitor failure.

  32. resolved Feb 01, 2026, 11:05 AM UTC

    Issue resolved on monitor recovery.

  33. investigating Feb 01, 2026, 11:19 AM UTC

    Issue re-opened on monitor failure.

  34. resolved Feb 01, 2026, 11:27 AM UTC

    Issue resolved on monitor recovery.

  35. investigating Feb 01, 2026, 11:34 AM UTC

    Issue re-opened on monitor failure.

  36. resolved Feb 01, 2026, 11:36 AM UTC

    Issue resolved on monitor recovery.

  37. investigating Feb 01, 2026, 11:58 AM UTC

    Issue re-opened on monitor failure.

  38. resolved Feb 01, 2026, 12:14 PM UTC

    Issue resolved on monitor recovery.

  39. investigating Feb 01, 2026, 12:20 PM UTC

    Issue re-opened on monitor failure.

  40. resolved Feb 01, 2026, 12:39 PM UTC

    Issue resolved on monitor recovery.

  41. investigating Feb 01, 2026, 12:42 PM UTC

    Issue re-opened on monitor failure.

  42. resolved Feb 01, 2026, 12:46 PM UTC

    Issue resolved on monitor recovery.

  43. investigating Feb 01, 2026, 12:50 PM UTC

    Issue re-opened on monitor failure.

  44. resolved Feb 01, 2026, 01:09 PM UTC

    Issue resolved on monitor recovery.

  45. investigating Feb 01, 2026, 01:17 PM UTC

    Issue re-opened on monitor failure.

  46. resolved Feb 01, 2026, 01:28 PM UTC

    Issue resolved on monitor recovery.

  47. investigating Feb 01, 2026, 01:30 PM UTC

    Issue re-opened on monitor failure.

  48. resolved Feb 01, 2026, 01:31 PM UTC

    Issue resolved on monitor recovery.

  49. investigating Feb 01, 2026, 01:34 PM UTC

    Issue re-opened on monitor failure.

  50. resolved Feb 01, 2026, 01:43 PM UTC

    Issue resolved on monitor recovery.

  51. investigating Feb 01, 2026, 01:52 PM UTC

    Issue re-opened on monitor failure.

  52. resolved Feb 01, 2026, 02:06 PM UTC

    Issue resolved on monitor recovery.

  53. investigating Feb 01, 2026, 02:17 PM UTC

    Issue re-opened on monitor failure.

  54. resolved Feb 01, 2026, 02:27 PM UTC

    Issue resolved on monitor recovery.

  55. investigating Feb 01, 2026, 02:32 PM UTC

    Issue re-opened on monitor failure.

  56. resolved Feb 01, 2026, 02:36 PM UTC

    Issue resolved on monitor recovery.

  57. investigating Feb 01, 2026, 02:41 PM UTC

    Issue re-opened on monitor failure.

  58. resolved Feb 01, 2026, 02:52 PM UTC

    Issue resolved on monitor recovery.

  59. investigating Feb 01, 2026, 02:56 PM UTC

    Issue re-opened on monitor failure.

  60. resolved Feb 01, 2026, 03:04 PM UTC

    Issue resolved on monitor recovery.

  61. investigating Feb 01, 2026, 03:11 PM UTC

    Issue re-opened on monitor failure.

  62. resolved Feb 01, 2026, 03:24 PM UTC

    Issue resolved on monitor recovery.

  63. investigating Feb 01, 2026, 03:30 PM UTC

    Issue re-opened on monitor failure.

  64. resolved Feb 01, 2026, 03:48 PM UTC

    Issue resolved on monitor recovery.

  65. investigating Feb 01, 2026, 04:06 PM UTC

    Issue re-opened on monitor failure.

  66. resolved Feb 01, 2026, 04:18 PM UTC

    Issue resolved on monitor recovery.

  67. investigating Feb 01, 2026, 04:20 PM UTC

    Issue re-opened on monitor failure.

  68. resolved Feb 01, 2026, 04:25 PM UTC

    Issue resolved on monitor recovery.