On a a Monday morning, while entering notes on the Arena portal of the Montpellier academy, the page refuses to load. The browser spins aimlessly, and no explicit error message appears. Before concluding that there is a general outage, a few quick checks can distinguish a local problem from a server-side incident.
Arena as a multi-application portal: identifying what is really blocking
Arena is not a single application. It is a portal providing access to multiple academic services: I-Prof, EPSnet, professional messaging, the PAF, among others. When you can no longer connect, the first thing to do is to test another service from the same interface.
If I-Prof works but EPSnet remains inaccessible, you are likely facing an isolated incident with that application, not a global outage of Arena. This distinction changes everything: the reporting channel and the resolution time will not be the same.
In practice, you can also check Arena Academy Montpellier through tracking pages that aggregate user reports in real-time. These tools provide a trend but do not reflect the official diagnosis from the IT department.
Another often overlooked point: when academic messaging and Arena go down at the same time, it points to a broader network incident at the Occitanie infrastructure level, not to an application bug.
Local verification before reporting an Arena Montpellier outage
Before clogging support channels, three actions eliminate most false positives.
- Clear the browser cache and cookies, or open a private browsing window. Arena sessions sometimes expire without notification, and the browser tries to reuse an expired authentication token.
- Test the connection from another network. The Wi-Fi of a school establishment may block certain ports or subdomains. Using a mobile hotspot allows for a quick resolution.
- Try another browser or device. Some browser updates create temporary incompatibilities with the national education portals.
If Arena remains inaccessible after these three steps, the problem is likely on the server side. This is the time to proceed with reporting.
The official incident reporting circuit: ASAP2 and DSI Occitanie
Participatory outage reporting sites (TotalBug, Service Status) are useful for spotting trends. You can see if other users are experiencing the same blockage at the same time. However, these counters have no official value and do not trigger any technical intervention.
The circuit that moves things forward goes through ASAP2, the assistance portal of the Occitanie academic region. This portal is accessible at all times and allows you to submit an incident report, track its progress, and communicate with support teams.
You can access it in two ways: directly via the ASAP2 URL, or from Arena itself (under the “Resources and Tools” domain, in the “Assistance and IT” category). When Arena is completely inaccessible, only direct access works.
Preparing your incident report
For a quick diagnosis, the report must contain specific elements: the exact name of the application concerned (not just “Arena”), the time of the blockage, any error message, the browser used, and the connection network.
A precise report reduces the processing time for the DSI teams. A vague message like “Arena is not working” forces technicians to contact the user again to obtain this information, which delays resolution.
Bypassing Arena unavailability on a daily basis
In an establishment, an Arena outage lasting several hours poses concrete problems: blocked note entry, impossible access to exam convocations, pending service delegations.
Some applications accessible via Arena also have a direct URL. This is the case for EPSnet or I-Prof, which can sometimes remain reachable even when the Arena portal itself is down. Testing these direct accesses is worth it before considering that everything is blocked.
The role of the head of the establishment
For teachers who do not see certain applications in Arena, the blockage is not always technical. A service delegation must be activated by the head of the establishment to make tools like EPSnet visible. Without this delegation, the application simply does not appear in the portal, which can be confused with a malfunction.
If a colleague from the same establishment accesses a service that you do not see, it is probably a matter of rights, not an outage.
Academic messaging and Arena Montpellier: outages sometimes linked
Reports from staff indicate difficulties affecting both Arena and professional messaging simultaneously. This type of situation suggests an incident on the common infrastructure of the Occitanie academic region, which hosts both services.
In this case, resolution does not depend on user action. Only the DSI can intervene on the network infrastructure. A useful reflex: check ASAP2 to see if a global incident has already been reported, and avoid multiplying redundant reports.
The resolution time varies depending on the nature of the incident. A hardware failure generally takes longer than a restart of an application service, without being able to provide a typical timeframe applicable to all cases.
When Arena and messaging are simultaneously out of service, urgent exchanges between establishments often go through the departmental DSDEN phone lines. This backup channel remains the most reliable while waiting for restoration.
