All Systems Operational
OSPool
Operational
AP 23
Operational
AP 40
Operational
AP 41
Operational
AP42
Operational
AP 43
Operational
Jupyter Notebooks
Operational
OSPool GlidenWMS Frontend
Operational
OSPool Central Managers / Collectors
Operational
OSPool Site EPs
Operational
Open Science Data Federation
Operational
StashCache Redirector
Operational
CVMFS Synchronization
Operational
Data Federation Accounting Service
Operational
Caches
Operational
Pelican Director
Operational
Pelican Registry
Operational
Hosted CEs
Operational
Hosted CE Infrastructure
Operational
Message Bus
Operational
GlideinWMS Factory
Operational
OASIS
Operational
Network Monitoring Pipeline
Operational
Software Repositories
Operational
Yum Repos
Operational
GridCF Repo
Operational
OSG Hub
Operational
Accounting
Operational
GRACC Frontend
Operational
GRACC Backend
Operational
GRACC APEL Reporting
Operational
Websites
Operational
Display
Operational
Main Website
Operational
DNS
Operational
OSGConnect Website
Operational
Topology
Operational
Hosted Submit
Operational
Hosted Submit Infrastructure
Operational
Hosted GlideinWMS
Operational
IGWN GWMS Frontend
Operational
JLAB GWMS Frontend
Operational
GLUEX GWMS Frontend
Operational
UCSD CMS GWMS Frontend
Operational
UCSD CMS VO Collector
Operational
Kubernetes Infrastructure
Operational
Tiger
Operational
River
Operational
Tempest
Operational
PATh Facility
Operational
AP 1
Operational
AP 1 Origin
Operational
Collaborations
Operational
AP 23
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
AP43 maintenance Jul 28, 2026 13:00-17:00 UTC
The OSPool operations team needs to take AP43 (ap43.uw.osg-htc.org) offline for maintenance, and are planning to do so around 8 AM CDT on Tuesday (7/28) morning. The downtime is expected to take around 4 hours.
Jobs already in the condor queue at the time should not need to be re-submitted after the downtime, but running jobs will most likely be interrupted and set back to idle. Idle jobs will be able to run again after the AP comes back online. Any executables (e.g. tmux sessions) running on the AP itself will be terminated.
Posted on Jul 23, 2026 - 16:24 UTC
Jobs already in the condor queue at the time should not need to be re-submitted after the downtime, but running jobs will most likely be interrupted and set back to idle. Idle jobs will be able to run again after the AP comes back online. Any executables (e.g. tmux sessions) running on the AP itself will be terminated.
Posted on Jul 23, 2026 - 16:24 UTC