Skip to content
← Back to status

Frequently asked questions

What the statuses mean, how the SLA is calculated, outage notifications, and where to report problems.

About this page

What is status.kutaitimurkab.go.id?

The official status page for the digital services of the Kutai Timur Regency Government, run by the NOC of the Communication and Informatics Office (Diskominfo). It shows the state of the internet uplink, the core network and routers, the firewall, the servers and the DRC servers.

The page is public and needs no login.

How often are services checked?

Every service is checked automatically every 60 seconds for network reachability.

When a service fails its checks for 5 minutes in a row, an incident is opened automatically and the NOC team is notified at once. The incident closes automatically after the service has been back to normal for 5 minutes.

What do the statuses and colours mean?

Operational (green): working normally. Degraded performance (yellow): slow, or some functions affected. Partial outage (orange): part of the service unreachable. Major outage (red): service unreachable. Under maintenance (blue): scheduled work.

The daily bars under each service cover the past 90 days. Hover over a bar to see that day’s availability.

SLA

What is the SLA and how is it calculated?

The SLA (Service Level Agreement) is the monthly availability target of a service. Availability = successful checks ÷ checks that should have run that month. A check that was not recorded counts as unavailable.

The overall SLA on the home page is the combined availability of all services for the current month. Month-by-month details are on the SLA page.

Open the SLA page

What is the SLA target for each service?

Class I, core infrastructure (internet uplink, core network, network security, servers and DRC servers): 99.9%, or at most about 43 minutes of downtime per 30 days.

How is an outage handled?

Every incident goes through Investigating, Identified, Monitoring and Resolved. Progress is recorded on the timeline of the incident page.

Initial response and recovery targets: Critical ≤ 15 minutes and ≤ 4 hours, Major ≤ 30 minutes and ≤ 8 hours, Minor ≤ 1 hour and ≤ 24 hours.

View incident history

Is maintenance announced in advance?

Yes. Scheduled maintenance is announced on this page at least 3 working days ahead, with the affected services and expected duration. Subscribers receive an email before it starts.

Notifications and support

How do I get notified about outages?

Click Subscribe, enter your email address and choose the services to follow (all or selected ones). Emails are sent when an incident opens, on important updates, and when it is resolved. Every email has an unsubscribe link.

Subscribe to notifications

I have a problem using a service. Where do I report it?

Fill in the Report a problem form on the Support page. You get a ticket code by email right away and can follow the handling on the Check status page. You can also email noc@kutaitimurkab.go.id.

Normal reports are handled Monday–Friday 08:00–16:00 WITA: initial response ≤ 4 working hours, resolution ≤ 3 working days. Urgent reports (the service cannot be used at all and public services are held up) are handled around the clock: initial response ≤ 4 hours, resolution ≤ 24 hours.

This covers login problems, password resets, account activation and API integration requests.

Report a problemCheck report status

I found a cyber security incident. Where do I report it?

Report it to KUTIM-CSIRT, for example a defaced site, gambling or phishing pages on a government domain, a data leak, or a vulnerability. Helpdesk reports marked "Related to a cyber security incident" become urgent, are handled around the clock and are coordinated with KUTIM-CSIRT.

The KUTIM-CSIRT channel is for cyber security incidents only. Problems using a service go to the helpdesk.

csirt.kutaitimurkab.go.id

A service shows as operational but I cannot reach it. Why?

Status is checked from the Diskominfo network. If a service shows as operational but will not open for you, check your internet connection, try another network, or clear the browser cache. If it still fails, report it to the helpdesk with the time and the network you used.