Is Georgia Tech IT down?

Last checked 7m ago
Current status
Georgia Tech IT is up

No incidents right now.

Official status page: https://status.gatech.edu · Polled every 5 minutes · 126 components tracked

Georgia Tech IT is operational right now. Last checked 7m ago; the most recent incident resolved 4d ago.

Real-time Georgia Tech IT status, recent outages, and incident history — pulled directly from Georgia Tech IT's official status page at https://status.gatech.edu every 5 minutes. Pingoru tracks 126 Georgia Tech IT services and has captured 31 incidents in the last 90 days (99.53% uptime). Get email, Slack, Discord, or webhook alerts the moment Georgia Tech IT reports a new incident — free for 5 monitors, no credit card.

Users who monitor Georgia Tech IT also follow these Education services: Zoom Clever PowerSchool Seesaw Canva ClassLink Schoology Nearpod Houghton Mifflin Harcourt NWEA View all 6,000+ providers
Georgia Tech IT uptime 99.53% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 22m
    Started Sep 14, 2026, 01:18 PM UTC · Resolved Sep 14, 2026, 02:41 PM UTC
    IdentityBuzzAPI
    Timeline · 2 updates
    • investigating · Sep 14, 2026, 01:18 PM UTC

      OIT is aware of a problem with the Georgia Tech Roles System (GRS) that is preventing rules and overrides from being created, deleted, and evaluated. Existing entitlements and dependent access are not affected, but changes are not being processed at this time. This means that anyone seeking new access or expecting to lose access to anything where access is controlled by GRS will see no changes in either direction until the issue is resolved. Related downstream effects include not being able to access GRS logs in IAT or use GRS related BuzzAPI endpoints. Feel free to massage as necessary. As an aside, the GRS database is huge. This may take some time.

    • monitoring · Sep 14, 2026, 01:38 PM UTC

      OIT has implemented a fix believed to have resolved the issue affecting GRS. Administrators performed a restart of the database, and service has been restored. Support teams are currently monitoring the service to ensure changes continue to process normally

    Latest: OIT has implemented a fix believed to have resolved the issue affecting GRS. Administrators performed a restart of the database, and service has been restored. Support teams are cu…

  2. Resolved 1d 23h
    Started Sep 02, 2026, 08:39 PM UTC · Resolved Sep 04, 2026, 07:48 PM UTC
    Email and CalendaringOffice 365
    Timeline · 2 updates
    • monitoring · Sep 02, 2026, 08:39 PM UTC

      The majority of services are restored for most users, and we continue to observe broad service recovery. We recognize that some users may still experience residual impact, and addressing these remaining scenarios continues to be our highest priority. We’re actively progressing our mitigation efforts and closely monitoring service health as we work to ensure full recovery for all users.

    • monitoring · Sep 03, 2026, 12:37 PM UTC

      We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated. Next update by:

    Latest: We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, i…

  3. Resolved 3d 23h
    Started Aug 27, 2026, 05:10 PM UTC · Resolved Aug 31, 2026, 04:54 PM UTC
    IdentityGTED
    Timeline · 6 updates
    • investigating · Aug 27, 2026, 05:10 PM UTC

      Support staff have received reports from multiple sources indicating that some students and employees are not being assigned to GRS roles as expected based on the delayed GRS rule processing. We are also observing inconsistent LDAP query performance that is further impacting rule processing. The team is actively investigating these issues, addressing individual cases and broader patterns, and evaluating potential query rerouting and service-side changes to improve performance and reliability. The next update will be provided within 2 hours.

    • monitoring · Aug 27, 2026, 07:05 PM UTC

      Support staff investigated and identified a hardware bottleneck. They were able to resolve the issue causing the bottleneck and GRS performance is improving. Current estimates indicate it may take an additional 2-4 hours for the backlog to clear completely. The next update will be provided within 2 hours.

    • monitoring · Aug 27, 2026, 10:53 PM UTC

      Support staff remains actively engaged in monitoring system performance as GRS processing and backlog continues to improve.

    • monitoring · Aug 28, 2026, 11:46 AM UTC

      OIT continues to monitor GRS following the resolution of the hardware issue that caused processing delays. Approximately 93% of the backlog of pending role evaluations has been completed, and processing performance has continued to improve. However, some access assignments depend on other access assignments being completed first. This means that even though most records have been reviewed, some users may still be waiting for all of their access updates to be applied. Some students and employees may still experience delays while the remaining updates are processed.

    • monitoring · Aug 28, 2026, 04:08 PM UTC

      GRS continues to recover following the hardware issue that caused delays in role processing. At this time, support staff expect the remaining backlog to be processed by the end of the day. Support staff will continue monitoring the service until processing has fully returned to normal.

    • monitoring · Aug 31, 2026, 11:40 AM UTC

      GRS role processing went well over the weekend and it is believed the backlog has finally completed. Support is verifying with all stakeholders before giving the final all clear to resolve the issue

    Latest: GRS role processing went well over the weekend and it is believed the backlog has finally completed. Support is verifying with all stakeholders before giving the final all clear to…

  4. Resolved 1h 43m
    Started Aug 24, 2026, 02:16 PM UTC · Resolved Aug 24, 2026, 04:00 PM UTC
    NetworkDomain Name System (DNS)
    Timeline · 1 update
    • investigating · Aug 24, 2026, 02:16 PM UTC

      Beginning at 08:53 AM on August 24, users reported issues logging into GTIPAM DNS service. When attempting to login, users receive a 500 error. The service appears to be functioning normally with the exception of the login issue. Support staff are investigating and working to resolve the issue

    Latest: Beginning at 08:53 AM on August 24, users reported issues logging into GTIPAM DNS service. When attempting to login, users receive a 500 error. The service appears to be functionin…

  5. Resolved 3h 28m
    Started Aug 24, 2026, 01:01 PM UTC · Resolved Aug 24, 2026, 04:29 PM UTC
    IdentitySingleSignOn (SSO)
    Timeline · 2 updates
    • monitoring · Aug 24, 2026, 01:01 PM UTC

      Beginning at 8:10 AM on August 24, monitoring detected an outage affecting the Single Sign-On (SSO) service. As a result, users may have been unable to log in to applications that require SSO, including Banner Admin, Oscar, USG, Buzzport, Degree Audit, GTIPAM, andWorkday. Support staff have implemented a fix and are monitoring the situation

    • monitoring · Aug 24, 2026, 02:14 PM UTC

      Support staff report they haven't seen any problems since 08:50 AM. They are continuing to monitor the situation.

    Latest: Support staff report they haven't seen any problems since 08:50 AM. They are continuing to monitor the situation.

See the full Georgia Tech IT outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Georgia Tech IT outage history →

Or sign up free to get alerts when Georgia Tech IT breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →