Skip to main content
YUCTS Status

Install YUCTS Status

Add YUCTS Status to your home screen for quick access. The latest status you loaded stays available offline.

On iPhone and iPad (Safari)

  1. Tap the Share button in the toolbar.
  2. Choose “Add to Home Screen”.
  3. Tap “Add”.

On Mac (Safari)

Choose File › Add to Dock (macOS Sonoma or later).

On Chrome, Edge and Android

Use the install button below, or the install icon in the address bar / browser menu.

If your browser cannot install web apps, bookmark this page instead.

櫻佑旅遊 | 規劃一趟小旅行給自己。

OperationalMeasured by the latest checkLast checked now

Current status

Latest response
52 ms
Average (24 h)
91 ms
95th percentile (24 h)
287 ms
Slowest (24 h)
1,711 ms
Uptime · 24 hours
100.00%
Uptime · 30 days
100.000%
Monitoring coverage 100.0%
Uptime · 90 days
100.000%
Monitoring coverage 100.0%
Uptime · 365 days
99.999%
Monitoring coverage 100.0%

Response time

15-minute averages over the last 24 hours. The dashed line shows the slowest check in each step.

Use the left and right arrow keys to move between bars.

Status history

Each bar is one day. Grey bars mean no monitoring data — they are not counted as up.

Use the left and right arrow keys to move between bars.

Oct 26, 2026Uptime 100.000% · Monitoring coverage 98.7%Today

Service level objective

Availability target 99.90%. Overlapping incidents are counted once and planned maintenance is excluded.

30 daysMeeting target
100.000%
Successful checks
100.000%
Downtime
0 seconds
Incidents
0
Monitoring coverage
100.0%
100% of the error budget left
Measured since Oct 2, 2026
90 daysMeeting target
100.000%
Successful checks
100.000%
Downtime
0 seconds
Incidents
0
Monitoring coverage
100.0%
100% of the error budget left
Measured since Aug 3, 2026
365 daysMeeting target
99.997%
Successful checks
99.999%
Downtime
4 minutes
Incidents
1
Monitoring coverage
100.0%
97% of the error budget left
Measured since May 21, 2026

Recent incidents

How this service is monitored

Check interval
Every minute
Request
GET
Slow response threshold
1,000 ms
Content check
No
Considered reachable when
the server answers with any HTTP status below 500, confirmed from a second method before reporting an outage
Monitored since