← HonkWatch.com

Is Unl down in Belgium?

Unl has problems

People in Belgium: 0 reports in the last hour Official page: Partial outage reported, checked just now Our checks: loads from 35 of 35 places

1 open incident: Account Lifecycle Manager Partial Outage

Partial outage reported by Unl 1 of 141 parts affected: Information Security / PASM. Going on for 4 d 14 h. Updated 7 Nov, 22:35 UTC, just now · Official status page
Report a problem
Change country

Known issues (from IT's status page)

Incidents

  • Account Lifecycle Manager Partial Outage (investigating, minor impact) Since 29 Oct, 20:27 UTC. Affects PASM · Details Latest update (29 Oct, 20:27 UTC): https://nebraska.accountlifecyclecloud.com/ web portal is intermittently slow/unresponsive. The ALM engine that connects to the NEAD Active Directory domain is offline. Impact: New managed account requests for the NEAD domain are unable to be provisioned. Existing accounts will continue to function

Maintenance

  • Communication and Collaboration / Poppulo Harmony - Digital Signage Downtime Saturday November 7 - Sunday November 8. (under way) 7 Nov, 14:00 UTC to 9 Nov, 02:00 UTC. Affects Digital Signage · Details Latest update (7 Nov, 14:00 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • Server Hosting - Linux impaired service (planned) 8 Nov, 03:00 UTC to 8 Nov, 07:00 UTC · Details Latest update (2 Nov, 17:38 UTC): RFC 265148: Server Hosting - Linux servers will have reduced performance during maintenance. Direct impact: Linux servers, Tier 0, ITS ADS, SNR, Systems, and other group, will be restarted to apply patches. ITS will apply OS and software patches during this time. <small><em> Questions 402-472-3970 o
  • Network Backbone impaired service (planned) 8 Nov, 12:00 UTC to 8 Nov, 21:00 UTC. Affects Network Backbone · Details Latest update (23 Oct, 13:29 UTC): RFC 261553: WAN in Kearney will have reduced performance during maintenance. Regular campus users may experience a traffic delay switching to an alternate path. UNK-ITEC and NU Foundation will see a short outage as the device reloads. <small><em> Questions 402-472-3970 or [email protected] </em>
Show 7 more maintenance windows
  • NeSIS - PeopleSoft System upgrade including Mavlink, MyBlue, MyCSC, MyNCTA, MyPSC, MyRecords, MyRED and WildcatsOnline (planned) 9 Nov, 05:00 UTC to 9 Nov, 08:00 UTC. Affects MyBlue, MyRecords, MyRed, Mavlink and 3 more · Details Latest update (29 Jul 2026, 16:50 UTC): We will be undergoing scheduled maintenance during this time.
  • Windows Server Monthly Maintenance (planned) 15 Nov, 03:00 UTC to 15 Nov, 17:00 UTC · Details Latest update (6 Nov, 20:57 UTC): RFC 266211: Performing Monthly Windows Server maintenance. <small><em> Questions 402-472-3970 or [email protected] </em>
  • Windows Server Monthly Maintenance (planned) 15 Nov, 08:00 UTC to 15 Nov, 17:00 UTC · Details Latest update (6 Nov, 20:58 UTC): RFC 266216: Performing Monthly Windows Server maintenance. <small><em> Questions 402-472-3970 or [email protected] </em>
  • NESIS fall maintenance downtime (planned) 16 Nov, 01:00 UTC to 16 Nov, 10:00 UTC · Details Latest update (29 Oct, 13:27 UTC): RFC 244639: NeSIS System including Mavlink, MyBlue, MyCSC, MyNCTA, MyPSC, MyRecords, MyRED and WildcatsOnline will be unavailable while the patch is being applied. <small><em> Questions 402-472-3970 or [email protected] </em>
  • NeSIS - PeopleSoft System upgrade including Mavlink, MyBlue, MyCSC, MyNCTA, MyPSC, MyRecords, MyRED and WildcatsOnline (planned) 16 Nov, 05:00 UTC to 16 Nov, 08:00 UTC. Affects MyBlue, MyRecords, MyRed, Mavlink and 3 more · Details Latest update (29 Jul 2026, 16:48 UTC): We will be undergoing scheduled maintenance during this time.
  • Windows Server Monthly Maintenance (planned) 22 Nov, 03:00 UTC to 22 Nov, 17:00 UTC · Details Latest update (6 Nov, 20:58 UTC): RFC 266217: Performing Monthly Windows Server maintenance. <small><em> Questions 402-472-3970 or [email protected] </em>
  • Network Backbone impaired service (planned) 22 Nov, 12:00 UTC to 22 Nov, 21:00 UTC. Affects Network Backbone · Details Latest update (5 Nov, 21:51 UTC): RFC 262289: WAN in Bellevue will have reduced performance during maintenance. Regular campus users may experience a traffic delay when switching to an alternative path. <small><em> Questions 402-472-3970 or [email protected] </em>

We keep the first 10 of 20 maintenance windows; the rest are on IT's status page.

In IT's own words, as we read them every 2.5 minutes, last just now. Read IT's status page

Reports from people in Belgium

Last 24 hours · Belgium · times in UTC

0 reports

No community reports in the last 24 hours from Belgium. Having trouble? Add your report.

Status page: partial outage, 3 Nov, 08:27 to now 024 00:0006:0012:0018:00 22:45-22:55 UTC: 34 of 34 places loaded it, typical 1110 to 1140 ms22:55-23:10 UTC: 35 of 35 places loaded it, typical 1132 to 1226 ms23:10-23:15 UTC: 34 of 34 places loaded it, typical 1198 ms23:15-23:20 UTC: 33 of 33 places loaded it, typical 1177 ms23:20-23:25 UTC: 35 of 35 places loaded it, typical 1112 ms23:25-23:30 UTC: 33 of 33 places loaded it, typical 1104 ms23:30-00:40 UTC: 35 of 35 places loaded it, typical 1079 to 1243 ms00:40-00:45 UTC: 34 of 34 places loaded it, typical 1224 ms00:45-00:55 UTC: 35 of 35 places loaded it, typical 1306 to 1317 ms00:55-01:00 UTC: 33 of 33 places loaded it, typical 1180 ms01:00-01:05 UTC: 34 of 34 places loaded it, typical 1145 ms01:05-01:30 UTC: 35 of 35 places loaded it, typical 1119 to 1245 ms01:30-01:35 UTC: 34 of 34 places loaded it, typical 1146 ms01:35-01:40 UTC: 35 of 35 places loaded it, typical 1122 ms01:40-01:45 UTC: 34 of 34 places loaded it, typical 1159 ms01:45-01:55 UTC: 35 of 35 places loaded it, typical 1098 to 1200 ms01:55-02:00 UTC: 34 of 34 places loaded it, typical 1226 ms02:00-02:10 UTC: 35 of 35 places loaded it, typical 1083 to 1230 ms02:10-02:15 UTC: 34 of 34 places loaded it, typical 1144 ms02:15-03:55 UTC: 35 of 35 places loaded it, typical 1094 to 1326 ms03:55-04:00 UTC: 33 of 33 places loaded it, typical 1294 ms04:00-04:10 UTC: 35 of 35 places loaded it, typical 1147 to 1302 ms04:10-04:15 UTC: 34 of 34 places loaded it, typical 1232 ms04:15-06:10 UTC: 35 of 35 places loaded it, typical 1096 to 1256 ms06:10-06:15 UTC: 34 of 34 places loaded it, typical 1225 ms06:15-06:30 UTC: 35 of 35 places loaded it, typical 1184 to 1330 ms06:30-06:35 UTC: 34 of 34 places loaded it, typical 1202 ms06:35-06:45 UTC: 35 of 35 places loaded it, typical 1157 to 1241 ms06:45-06:50 UTC: 34 of 34 places loaded it, typical 1146 ms06:50-07:00 UTC: 35 of 35 places loaded it, typical 1099 to 1112 ms07:00-07:05 UTC: 34 of 34 places loaded it, typical 1088 ms07:05-08:25 UTC: 35 of 35 places loaded it, typical 1083 to 1257 ms08:25-08:30 UTC: 34 of 34 places loaded it, typical 1128 ms08:30-08:40 UTC: 35 of 35 places loaded it, typical 1143 to 1183 ms08:40-08:45 UTC: 34 of 34 places loaded it, typical 1251 ms08:45-08:55 UTC: 35 of 35 places loaded it, typical 1120 to 1146 ms08:55-09:00 UTC: 34 of 34 places loaded it, typical 1139 ms09:00-09:10 UTC: 35 of 35 places loaded it, typical 1218 to 1223 ms09:10-09:15 UTC: 34 of 34 places loaded it, typical 1205 ms09:15-09:20 UTC: 30 of 30 places loaded it, typical 1199 ms09:20-09:40 UTC: 35 of 35 places loaded it, typical 1184 to 1344 ms09:40-09:45 UTC: 34 of 34 places loaded it, typical 1188 ms09:45-09:55 UTC: 35 of 35 places loaded it, typical 1164 to 1216 ms09:55-10:00 UTC: 34 of 34 places loaded it, typical 1209 ms10:00-10:10 UTC: 35 of 35 places loaded it, typical 1235 to 1287 ms10:10-10:15 UTC: 34 of 34 places loaded it, typical 1192 ms10:15-10:20 UTC: 20 of 20 places loaded it, typical 1301 ms10:20-10:35 UTC: 35 of 35 places loaded it, typical 1184 to 1311 ms10:35-10:40 UTC: 34 of 34 places loaded it, typical 1273 ms10:40-10:55 UTC: 35 of 35 places loaded it, typical 1127 to 1250 ms10:55-11:00 UTC: 34 of 34 places loaded it, typical 1249 ms11:00-11:10 UTC: 35 of 35 places loaded it, typical 1180 to 1246 ms11:10-11:15 UTC: 34 of 34 places loaded it, typical 1169 ms11:15-11:25 UTC: 35 of 35 places loaded it, typical 1145 to 1233 ms11:25-11:30 UTC: 34 of 34 places loaded it, typical 1267 ms11:30-11:35 UTC: 35 of 35 places loaded it, typical 1181 ms11:35-11:40 UTC: 17 of 17 places loaded it, typical 1246 ms11:40-11:55 UTC: 35 of 35 places loaded it, typical 1122 to 1165 ms11:55-12:00 UTC: 34 of 34 places loaded it, typical 1219 ms12:00-12:30 UTC: 35 of 35 places loaded it, typical 1127 to 1321 ms12:30-12:35 UTC: 34 of 34 places loaded it, typical 1214 ms12:35-12:50 UTC: 35 of 35 places loaded it, typical 1116 to 1255 ms12:50-12:55 UTC: 34 of 34 places loaded it, typical 1230 ms12:55-13:00 UTC: 35 of 35 places loaded it, typical 1240 ms13:00-13:05 UTC: 34 of 34 places loaded it, typical 1237 ms13:05-13:15 UTC: 35 of 35 places loaded it, typical 1115 to 1188 ms13:15-13:20 UTC: 34 of 34 places loaded it, typical 1136 ms13:20-14:40 UTC: 35 of 35 places loaded it, typical 1111 to 1326 ms14:40-14:45 UTC: 34 of 34 places loaded it, typical 1117 ms14:45-14:55 UTC: 35 of 35 places loaded it, typical 1064 to 1264 ms14:55-15:00 UTC: 34 of 34 places loaded it, typical 1147 ms15:00-15:10 UTC: 35 of 35 places loaded it, typical 1204 to 1228 ms15:10-15:15 UTC: 34 of 34 places loaded it, typical 1270 ms15:15-15:25 UTC: 35 of 35 places loaded it, typical 1222 to 1224 ms15:25-15:30 UTC: 34 of 34 places loaded it, typical 1157 ms15:30-15:40 UTC: 35 of 35 places loaded it, typical 1202 to 1251 ms15:40-15:45 UTC: 34 of 34 places loaded it, typical 1236 ms15:45-15:55 UTC: 35 of 35 places loaded it, typical 1233 to 1261 ms15:55-16:00 UTC: 34 of 34 places loaded it, typical 1208 ms16:00-16:10 UTC: 35 of 35 places loaded it, typical 1188 to 1221 ms16:10-16:15 UTC: 34 of 34 places loaded it, typical 1147 ms16:15-16:25 UTC: 35 of 35 places loaded it, typical 1143 to 1154 ms16:25-16:35 UTC: 34 of 34 places loaded it, typical 1172 to 1308 ms16:35-16:55 UTC: 35 of 35 places loaded it, typical 1139 to 1369 ms16:55-17:05 UTC: 34 of 34 places loaded it, typical 1122 to 1264 ms17:05-17:10 UTC: 35 of 35 places loaded it, typical 1108 ms17:10-17:15 UTC: 33 of 33 places loaded it, typical 1185 ms17:15-17:25 UTC: 35 of 35 places loaded it, typical 1212 to 1245 ms17:25-17:30 UTC: 34 of 34 places loaded it, typical 1154 ms17:30-18:20 UTC: 35 of 35 places loaded it, typical 1151 to 1389 ms18:20-18:25 UTC: 34 of 34 places loaded it, typical 1355 ms18:25-18:55 UTC: 35 of 35 places loaded it, typical 1124 to 1265 ms18:55-19:00 UTC: 34 of 34 places loaded it, typical 1320 ms19:00-19:05 UTC: 35 of 35 places loaded it, typical 1249 ms19:05-19:10 UTC: 33 of 33 places loaded it, typical 1304 ms19:10-19:25 UTC: 35 of 35 places loaded it, typical 1208 to 1252 ms19:25-19:30 UTC: 34 of 34 places loaded it, typical 1199 ms19:30-19:55 UTC: 35 of 35 places loaded it, typical 1219 to 1342 ms19:55-20:00 UTC: 33 of 33 places loaded it, typical 1234 ms20:00-20:15 UTC: 35 of 35 places loaded it, typical 1137 to 1310 ms20:15-20:20 UTC: 34 of 34 places loaded it, typical 1290 ms20:20-20:25 UTC: 35 of 35 places loaded it, typical 1164 ms20:25-20:30 UTC: 34 of 34 places loaded it, typical 1286 ms20:30-20:45 UTC: 35 of 35 places loaded it, typical 1130 to 1222 ms20:45-20:50 UTC: 34 of 34 places loaded it, typical 1231 ms20:50-20:55 UTC: 35 of 35 places loaded it, typical 1098 ms20:55-21:00 UTC: 34 of 34 places loaded it, typical 1163 ms21:00-21:15 UTC: 35 of 35 places loaded it, typical 1137 to 1225 ms21:15-21:20 UTC: 34 of 34 places loaded it, typical 1119 ms21:20-21:55 UTC: 35 of 35 places loaded it, typical 1136 to 1324 ms21:55-22:00 UTC: 34 of 34 places loaded it, typical 1155 ms22:00-22:05 UTC: 35 of 35 places loaded it, typical 1154 ms22:05-22:10 UTC: 34 of 34 places loaded it, typical 1289 ms22:10-22:35 UTC: 35 of 35 places loaded it, typical 1166 to 1246 ms22:35-22:40 UTC: 4 of 4 places loaded it, typical 1463 ms Typical response time of the places that loaded it, at most 1463 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Unl's status page showed a partial outage, a major outage, as we read it every 2.5 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded unl.edu in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Belgium only.

Latest checks, 22:35-22:40 UTC: 4 of 4 places loaded it, typical 1463 ms.

Report totals as of 7 Nov, 22:36 UTC

Report a problem with Unl

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Belgium

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Belgium. The report chart above is filtered to Belgium.

Our own checks of unl.edu

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Melbourne: loaded in 1772 ms Hong Kong: loaded in 1564 ms Seattle: loaded in 495 ms Jakarta: loaded in 1362 ms Los Angeles: loaded in 1241 ms Santiago: loaded in 1281 ms Madrid: loaded in 914 ms Bangalore: loaded in 2970 ms Tokyo: loaded in 1730 ms Singapore: loaded in 1963 ms Lauterbourg: loaded in 1156 ms Doha: loaded in 1557 ms St. Louis: loaded in 360 ms Cape Town: loaded in 2930 ms Toronto: loaded in 279 ms Portsmouth: loaded in 824 ms Amsterdam: loaded in 940 ms Warsaw: loaded in 1360 ms Querétaro: loaded in 401 ms São Paulo: loaded in 876 ms Sydney: loaded in 2352 ms Port Louis: loaded in 3573 ms London: loaded in 811 ms Delhi: loaded in 2118 ms New Jersey: loaded in 284 ms Mumbai: loaded in 2627 ms Atlanta: loaded in 289 ms Osaka: loaded in 1495 ms Johannesburg: loaded in 1478 ms Seoul: loaded in 1130 ms Hamina: loaded in 838 ms Frankfurt: loaded in 1306 ms Tel Aviv: loaded in 1230 ms New York: loaded in 569 ms Dallas: loaded in 1454 ms
  • MelbourneReachable1772 ms, 1 min ago
  • Hong KongReachable1564 ms, 1 min ago
  • SeattleReachable495 ms, 1 min ago
  • JakartaReachable1362 ms, 1 min ago
  • Los AngelesReachable1241 ms, 1 min ago
  • SantiagoReachable1281 ms, 1 min ago
  • MadridReachable914 ms, 1 min ago
  • BangaloreReachable2970 ms, 1 min ago
  • TokyoReachable1730 ms, 1 min ago
  • SingaporeReachable1963 ms, 2 min ago
  • LauterbourgReachable1156 ms, 2 min ago
  • DohaReachable1557 ms, 2 min ago
  • St. LouisReachable360 ms, 2 min ago
  • Cape TownReachable2930 ms, 2 min ago
  • TorontoReachable279 ms, 2 min ago
  • PortsmouthReachable824 ms, 2 min ago
  • AmsterdamReachable940 ms, 2 min ago
  • WarsawReachable1360 ms, 2 min ago
  • QuerétaroReachable401 ms, 2 min ago
  • São PauloReachable876 ms, 2 min ago
  • SydneyReachable2352 ms, 2 min ago
  • Port LouisReachable3573 ms, 2 min ago
  • LondonReachable811 ms, 2 min ago
  • DelhiReachable2118 ms, 2 min ago
  • New JerseyReachable284 ms, 2 min ago
  • MumbaiReachable2627 ms, 2 min ago
  • AtlantaReachable289 ms, 2 min ago
  • OsakaReachable1495 ms, 3 min ago
  • JohannesburgReachable1478 ms, 3 min ago
  • SeoulReachable1130 ms, 3 min ago
  • HaminaReachable838 ms, 3 min ago
  • FrankfurtReachable1306 ms, 3 min ago
  • Tel AvivReachable1230 ms, 3 min ago
  • New YorkReachable569 ms, 3 min ago
  • DallasReachable1454 ms, 3 min ago

This is separate from the status page: we request unl.edu and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Unl

IT

Information Security

  • PASMDegraded

Communication & Collaboration

  • Digital SignageMaintenance

139 other parts are working.

Incidents and maintenance

Open incidents

  • Account Lifecycle Manager Partial Outage (investigating) Since 29 Oct, 20:27 UTC. Affects PASM · Details

Maintenance

  • Communication and Collaboration / Poppulo Harmony - Digital Signage Downtime Saturday November 7 - Sunday November 8. (now) 7 Nov, 14:00 UTC to 9 Nov, 02:00 UTC. Affects Digital Signage · Details
  • Server Hosting - Linux impaired service (planned) 8 Nov, 03:00 UTC to 8 Nov, 07:00 UTC · Details
  • Network Backbone impaired service (planned) 8 Nov, 12:00 UTC to 8 Nov, 21:00 UTC. Affects Network Backbone · Details
  • NeSIS - PeopleSoft System upgrade including Mavlink, MyBlue, MyCSC, MyNCTA, MyPSC, MyRecords, MyRED and WildcatsOnline (planned) 9 Nov, 05:00 UTC to 9 Nov, 08:00 UTC. Affects MyBlue, MyRecords, MyRed, Mavlink and 3 more · Details
  • Windows Server Monthly Maintenance (planned) 15 Nov, 03:00 UTC to 15 Nov, 17:00 UTC · Details
  • Windows Server Monthly Maintenance (planned) 15 Nov, 08:00 UTC to 15 Nov, 17:00 UTC · Details
  • NESIS fall maintenance downtime (planned) 16 Nov, 01:00 UTC to 16 Nov, 10:00 UTC · Details
  • NeSIS - PeopleSoft System upgrade including Mavlink, MyBlue, MyCSC, MyNCTA, MyPSC, MyRecords, MyRED and WildcatsOnline (planned) 16 Nov, 05:00 UTC to 16 Nov, 08:00 UTC. Affects MyBlue, MyRecords, MyRed, Mavlink and 3 more · Details
  • Windows Server Monthly Maintenance (planned) 22 Nov, 03:00 UTC to 22 Nov, 17:00 UTC · Details
  • Network Backbone impaired service (planned) 22 Nov, 12:00 UTC to 22 Nov, 21:00 UTC. Affects Network Backbone · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 3 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

3 Nov, 08:27 UTCPartial outagegoing on, 4 d 14 h1 of 141 parts affected: Information Security / PASM
What can I try?

Having trouble with Unl?

  1. Compare reports from Belgium and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Unl down, or is it just me?

Unl itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Unl status page and load unl.edu from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Education

Each card shows that service's own status, not Unl's. A problem listed here does not mean Unl has one.

See the live outage feed for Belgium · Find another service