📈 Live Status: 🟧 Partial outage

This repository contains the open-source uptime monitor and status page for Sabari Vijayan, powered by Upptime.

With Upptime, you can get your own unlimited and free uptime monitor and status page, powered entirely by a GitHub repository. We use Issues as incident reports, Actions as uptime monitors, and Pages for the status page.

URL	Status	History	Response Time	Uptime
KTU Main Website	🟩 Up	ktu-main-website.yml	5980ms	41.00%
e-Governance Portal	🟥 Down	e-governance-portal.yml	4495ms	82.66%
Results Portal	🟩 Up	results-portal.yml	2756ms	41.00%
Certificate Verification	🟩 Up	certificate-verification.yml	3470ms	41.00%
Academic Calendar	🟩 Up	academic-calendar.yml	3598ms	41.00%

Visit our status website →

📊 Monitoring Details

This dashboard provides high-frequency monitoring of critical KTU portals to ensure transparency and accessibility for students and faculty.

🕒 Frequency of Checks

• Uptime Monitoring: Checked every 5 minutes.
• Response Time Tracking: Recorded every 30 minutes.
• Graphs & Data Updates: Summaries and visualizations are regenerated every hour.

📅 Historical Monitoring Notes (for Data Analysis)

If you are performing historical analysis on the data in this repository, please note the following frequency changes:

• Before April 26, 2026: Response time checks were performed approximately 1-2 times per day (daily summary).
• From April 26, 2026 onwards: Response time tracking was increased to every 30 minutes to provide more granular performance data.
• Uptime Monitoring: Has consistently been maintained at 5-minute intervals since project inception.

🔍 Tracking Methodology

• Uptime Monitoring: We use GitHub Actions to ping each endpoint every 5 minutes. A site is considered Up only if it returns a 2xx HTTP status code.
• Response Time: We measure the latency of each portal every 30 minutes to track performance trends and detect slowdowns.
• Error Detection & Codes:
  • HTTP Failures: Any response code outside the 200-299 range (e.g., 403 Forbidden, 404 Not Found, 500 Internal Server Error, 503 Service Unavailable) triggers a downtime alert.
  • Content Validation: For critical portals, we check for specific "down" indicators in the response body (e.g., "Internal Server Error" text) to catch failures that might improperly return a 200 OK status.
  • SSL/TLS: We monitor SSL certificate validity to ensure secure access.

📥 Data Usage

If you are using the raw data from the history/ or api/ directories for your own analysis, please ensure you perform a git pull first. The data is updated automatically by our automated workflows multiple times per hour.

📄 License

• Powered by: Upptime
• Code: MIT © Anand Chowdhary, supported by Pabio
• Data in the ./history directory: Open Database License