Over the past few days, many FACEIT stats tools have stopped working reliably: ELO timelines show gaps, match histories are incomplete, and some overlays display outdated or incorrect values. This is not a streamer-side “bug” – it’s the result of a technical change at the API level.
Important: This involved an internal endpoint used by the FACEIT website itself – not an officially documented public API. Restricting access to such endpoints is fully understandable, as it ultimately comes down to stability, load protection, and platform security.
What exactly was restricted?
Many third-party tools were pulling data from an internal (non-public) API used by the FACEIT website. These endpoints are not intended for external usage. Once they are heavily accessed by bots or tools, the risk increases that:
- • Request volume explodes and the platform becomes unstable
- • Rate limits and blocking rules must become more aggressive
- • Abuse and scraping unnecessarily strain the infrastructure
That’s why restricting access to this endpoint is completely reasonable – to ensure platform stability.
Why do many tools now have ELO gaps?
If a tool does not store historical ELO data itself, but instead fetches it live on every request, it immediately runs into problems once the endpoint is no longer available:
- • ELO timeline breaks
- • Matches suddenly go missing
- • Overlays show outdated values
- • Commands like !elo become unreliable
- • ELO changes are stored persistently
- • History remains consistent
- • Gaps can be filled retroactively
- • Overlay & commands remain stable
Why registered users remain gap-free with us
Our system continuously processes matches. Once a user is registered, ELO deltas and match data are persisted instead of being fetched live only. This allows us to:
In practical terms:
- ✓ Process and store matches reliably
- ✓ Detect ELO gaps and automatically recalculate them
- ✓ Guarantee gap-free ELO data for registered users
- ✓ Power commands and overlays from stable internal data
Gaps may occur because historical data cannot always be fully reconstructed if it was never stored in the first place. This is technically normal and currently affects many tools.
From the moment of registration, matches are permanently processed. This keeps ELO history, match data, overlays, and !elo consistent – without dependency on internal web endpoints.
Does this affect the ELO command and the overlay?
Yes – for systems that depend live on the affected endpoints. In our case, both overlay and !elo rely on internally stored match data, which keeps values stable for registered users.
- ✓ !elo remains accurate because ELO data is persisted internally
- ✓ Overlay shows consistent values even if external endpoints change
- ✓ Match gaps are detected and automatically synchronized
Conclusion
FACEIT protecting internal endpoints is both correct and necessary. The real issue only affects tools that rely entirely on pulling historical data live from such endpoints.
If you want gap-free ELO data and stable stream displays, you need a system that processes matches independently and permanently stores ELO changes – so commands and overlays don’t break just because external endpoints change.
Note: Unregistered profiles may show gaps because historical data cannot always be fully reconstructed.
FAQ
Because it was an internal website interface. Blocking it is a normal step to ensure platform stability, load protection, and abuse prevention.
Because they did not store historical data persistently and relied on a live endpoint that is no longer available.
Yes. The system processes matches and stores ELO deltas internally, allowing gaps to be detected and synchronized.
For live-only tools, yes. For registered users, command and overlay remain stable because they are powered by internal match data.