Skip to main content
YUCTS Status

Language

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.

System history

Long-term reliability of every service, the incident trend and how the numbers are calculated.

167 incidents and 7 maintenance windows in this period. (Nov 2, 2025 – Nov 1, 2026, UTC)

Reliability by service

Monthly · 13 monthsNov 2, 2025 – Nov 1, 2026Dates in UTC

  • Normal
  • Degraded performance
  • Outage
  • Planned maintenance
  • No monitoring data
  • Incident recorded

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

99.999%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

NormalUptime 100.00%

Normal days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
1
Outage time (incident records)
4 minutes
Data coverage
100.0%since monitoring began on May 22, 2026

Monitoring began on May 22, 2026. The 201 days before it are shown as “no monitoring data”. Data on 164 of 365 days

櫻佑旅遊🌸航空旅遊資訊網

99.885%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

Degraded performanceUptime 100.00%

Normal days
0
Degraded days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
91
Outage time (incident records)
8 hours 36 minutes
Data coverage
100.0%since monitoring began on May 22, 2026

Monitoring began on May 22, 2026. The 201 days before it are shown as “no monitoring data”. Data on 164 of 365 days

YucDu 佑瑄 | 好きなことを、好きなだけ。

99.893%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

NormalUptime 100.00%

Normal days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
71
Outage time (incident records)
7 hours 42 minutes
Data coverage
100.0%since monitoring began on May 22, 2026

Monitoring began on May 22, 2026. The 201 days before it are shown as “no monitoring data”. Data on 164 of 365 days

Yucts 文檔

100.000%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

NormalUptime 100.00%

Normal days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
0
Outage time (incident records)
0 seconds
Data coverage
100.0%since monitoring began on May 30, 2026

Monitoring began on May 30, 2026. The 209 days before it are shown as “no monitoring data”. Data on 156 of 365 days

YUCTS Transit

99.961%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

Degraded performanceUptime 100.00%

Normal days
0
Degraded days
1
Maintenance days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
5
Outage time (incident records)
13 minutes
Data coverage
97.5%since monitoring began on Oct 23, 2026

Monitoring began on Oct 23, 2026. The 355 days before it are shown as “no monitoring data”. Data on 10 of 365 days

YUCTS Search

100.000%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

NormalUptime 100.00%

Normal days
1
Maintenance days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
0
Outage time (incident records)
0 seconds
Data coverage
100.0%since monitoring began on Oct 30, 2026

Monitoring began on Oct 30, 2026. The 362 days before it are shown as “no monitoring data”. Data on 3 of 365 days

YUCTS 旅遊優惠

100.000%Uptime · 365 days

Nov 2026Nov 1 · 1 of 30 days fall in this range

NormalUptime 100.00%

Normal days
1
Incidents
0
Checks
812

Use the arrow keys, Home and End to move between periods. Enter opens the days of a week or month; Escape goes back.

Incidents
0
Outage time (incident records)
0 seconds
Data coverage
100.0%since monitoring began on Oct 30, 2026

Monitoring began on Oct 30, 2026. The 362 days before it are shown as “no monitoring data”. Data on 3 of 365 days

  • Weekly and monthly uptime is weighted by the actual numbers of successful and total checks, not averaged from daily percentages. A short outage marks its day without colouring the whole week or month.
  • Uptime comes from every check; outage time comes from incident records (major and critical incidents, excluding planned maintenance). The sources differ, so the two numbers need not match.
  • One incident can affect several services, so the per-service counts can add up to more than the site-wide total.
  • Data coverage is the share of expected checks recorded since the service was added to monitoring. Days before that, or without results, are shown as “no monitoring data” and count neither as up nor as down.

Incident trend

Incidents started per month, by severity.

MaintenanceMinorMajorCritical

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

Data table
StartedMinorMajorCriticalMaintenance
Nov 20250000
Dec 20250000
Jan 20260000
Feb 20260000
Mar 20260000
Apr 20260000
May 202603900
Jun 202606904
Jul 202601300
Aug 20260200
Sep 202601000
Oct 202602604
Nov 20260000

How we measure

  1. Each service is checked every minute from Cloudflare’s network with an HTTP request (8-second timeout, up to two retries 3 seconds apart).
  2. Before an outage is reported, the result is confirmed with a second method (a browser-like HEAD and GET with cache bypass). If either method gets an answer, the service is not reported down.
  3. Responses slower than the service’s threshold (1 second by default) are reported as slow; some services must be slow in several checks in a row first. A failed content check is also reported as slow.
  4. An incident opens automatically after a confirmed outage and closes after five consecutive successful checks. The YUCTS team can also post incidents and updates manually.
  5. Uptime is the share of successful checks. Periods without checks (for example before a service was added) are shown as “no data” and are excluded rather than counted as up.
  6. Availability for the service level objective uses incident durations: overlapping incidents are merged, and planned maintenance windows are excluded from both the downtime and the measured time.
  7. Raw checks are kept for 24 hours and daily summaries for 365 days. All times are stored in UTC.