Lets hope that Go is also not used by MT (CVE-2026-111943) or other technology that fetches dependencies over HTTPS with certificates signed by eMudhra CA, these guys took seriously that 4 is strong random https://xkcd.com/221/ 
MikroTik, customers deserve better communication during downtime
As a MikroTik customer, I find the lack of communication surrounding the website downtime frustrating. I haven’t been able to find a clear announcement on X or another official channel explaining what is happening, which services are affected, or when we can expect another update.
If this downtime is a precaution related to the PHP vulnerabilities, that is understandable. Taking systems offline to protect them is a responsible decision. Leaving customers to guess why they are unavailable is not.
People rely on MikroTik products to run real networks and businesses. When your website becomes unavailable without an easily accessible explanation, customers have no way to tell whether this is scheduled maintenance, a security precaution, or a larger incident.
Frankly, that silence gives the impression of a poorly run company. A short announcement acknowledging the outage, explaining its scope, and providing a time for the next update would go a long way. An exact restoration time isn’t necessary if you don’t have one—just communicate.
MikroTik should have a public status page hosted independently of its main infrastructure, with updates shared through its official social accounts. That is a reasonable expectation for a networking vendor whose customers depend on reliability.
It’s a pity... This is actually an official channel!!!
(most of the others are fake)
And since you posted in this thread, you must have seen it...
Demanding a specific timeline when the issue does not depend on the company
and cannot be resolved directly by it
but rather by third parties,
is completely ridiculous and points to a certain level of internal frustration...
So you've found this. In which way your network gear was disrupted by mikrotik.com website being in maintenance? Sorry, the package server was still online all the time. What did you miss? Writing a long post for what?
Your network was offline and in big danger because the shiny website was down?
Not from MikroTik officially but still: https://mikrotikstat.us/
Check your /app containers...
Just be aware there are about dozen /app containers that use PHP. Now these are somewhat outside MikroTik direct control to patch, it's hard to know if all have the PHP fixes yet. Claude tell me the following /app use PHP, it may not be 100%, and you should check if any /app containers active are using PHP internally on your own.
PHP-based apps:
┌────────────┬─────────────────────────────────────────────────────────────────────────────────────┐
│ /app │ Image that runs PHP │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ wordpress │ docker.io/wordpress:latest │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ nextcloud │ docker.io/nextcloud:stable-apache │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ roundcube │ roundcube/roundcubemail:latest-fpm-alpine (php-fpm behind nginx) │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ librenms │ librenms/librenms │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ zabbix │ zabbix/zabbix-web-apache-mysql (only the web frontend; the server and agent are C) │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ snipeit │ snipe/snipe-it:latest (Laravel) │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ kimai │ kimai/kimai2:apache (Symfony) │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ wallabag │ wallabag/wallabag:latest (Symfony) │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ partdb │ jbtronics/part-db1:latest (Symfony) │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ filegator │ filegator/filegator:latest-multiarch │
├────────────┼─────────────────────────────────────────────────────────────────────────────────────┤
│ librespeed │ lscr.io/linuxserver/librespeed:latest (PHP backend for the results/telemetry pages) │
└────────────┴─────────────────────────────────────────────────────────────────────────────────────┘
Rough list, unverified by human
/app's auto-upgrade=yes may not be default...
RouterOS /app should update if you have the /app/settings/set auto-update=yes (and/or enabled on individual /app's "Auto Update" setting. The default here has changed, so cannot say which might be set.
You should be able to re-pull the containers manually.
Do your own homework if you use the /app containers.
I'll leave some better notification about /app and php2shell to MikroTik, so more "FYI" since I did not see the /app containers that MikroTik "ships" covered here.
They may not be "MikroTik" things, but worth a note since MikroTik does "ship" them...
Well, this was a shitshow yesterday. If I had to choose, do disclosures in the Mikrotik way. Not whatever happened yesterday around PHP.
Ref
> As a result of the leak and pre-announcement around 20:00 UTC, Calif, one of the security firms that had reported the issues, mistakenly published a video. It showed their proof of concept working against a number of targets and revealed a few additional, though limited, details about the vulnerabilities. Copies of the deleted video started circulating on social media soon after. The video contributed to accelerated development of various PoCs (exploitation proof of concepts), which then increased circulation on October 21st.
> On October 21st at 07:41 UTC, more than six hours before the coordinated release, Chainguard unilaterally broke the embargo and published built images containing the fix. Like other distributors, Chainguard had received the patch in advance so its users could update the moment the vulnerabilities were disclosed. Any attacker could now study the fix in binary form while every other PHP user was still waiting for the release. This disregarded weeks of work by many parties toward a coordinated disclosure.
What is a 6h compared to weeks of vulnerability being at wild?
- MikroTik official channels are the website and the forum (this).
- MikroTik does not ship "Apps" or containers at this point, they are empty Yaml templates. You are responsible for configuring and updating them.
Did you actually find them useful, or was it just to stir up not useful controversy?
And as far as I’m concerned, that’s how it should be.
It’s not as if companies should feel obligated to sign up for and manage every new social platform that gets invented.
This is not directly related to RouterOS.
This a bit of information for others that are using PHP and don't want to, or have no time right now to update and adapt PHP code to patch the problem. I used this page where in last part mitigations are mentioned to just disable the part that is vulnerable so it can't be called and be misused.
I also use OWASP CRS for my Apache server and that filters incoming traffic and when found harmful it won't reach Apache.
And the specific pull request for this: feat: block UA of php2shell PoC by azurit · Pull Request #4893 · coreruleset/coreruleset · GitHub
And is this offcial or apocryphal?
AFAIK they run:
- YouTube: https://www.youtube.com/mikrotik
- Instagram: https://www.instagram.com/mikrotik.world/
- X/Twitter: https://x.com/mikrotik_com
- TikTok: https://www.tiktok.com/@mikrotik_com
- Mastodon: About - mikrotik.social
All of them are "official", AFAIK, but maybe some are more offical as others 
There is an official Discord as well.
No Twitch or Snapchat 
? OK, back to topic... 
So which one is the most official channel then? Seriously! 
As @normis wrote, the website and the forum are the primary resources;
TikTube/YouTube are just for videos;
(see next posts)
The one the person interested in has access to and actively uses it.
That is not official
Please do not spread misinformation! Some of those are not run by mikrotik at all