Runah (@RunahOfficial) header
Runah (@RunahOfficial) profile picture

@Diam_Wall CEO & Founder & Dev @tapitgg Founder & Dev Streamer on: https://teapawt.net/t.co/GT1MtJOAPd Partnerships email: [email protected]

Lisbon, Portugal
Joined January 2017
Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)Photo by Runah (@RunahOfficial)
O ARTEX demonstra que estamos a entrar numa nova era da cibersegurança, em que os ataques já conseguem adaptar-se autonomamente. Na DiamWall, identificámos várias tentativas contra os nossos clientes, todas bloqueadas pelo nosso antibot, sem sequer ser necessário recorrer à WAF. É precisamente para enfrentar este tipo de ameaças que continuamos a desenvolver a nossa tecnologia. Orgulho no que estamos a construir e, sobretudo, nos resultados que já conseguimos demonstrar.
O número de empresas privadas e estatais a serem comprometidas, a sofrer de defacement e web shells não é ao acaso. Por trás de muitos destes ataques está o ARTEX, uma framework que usa inteligência artificial para encontrar falhas, explorá-las e voltar a tentar até conseguir entrar, sem nunca se cansar e com muito pouca intervenção humana. Na DiamWall acompanhamos o ARTEX há cerca de um mês e a nossa threat intelligence não deixa dúvidas: já está a ser usado em Portugal, com muitas entidades comprometidas só nos últimos dias. Foi direcionado a vários dos nossos clientes, diversas vezes, sem qualquer tipo de sucesso, porque o nosso antibot o impediu instantaneamente nos primeiros pedidos, sem que a WAF chegasse sequer a ser necessária. Uma WAF sozinha já não é suficiente, nem mesmo as maiores do mercado, na defesa contra agentes de IA que reescrevem o ataque até encontrarem uma variação que consiga ter sucesso. No nosso blog explicamos o que é o ARTEX, como detetá-lo nos seus logs e o que fazer já esta semana. diamwall.com/pt/blog/post/ar…
18
3,194
O ARTEX demonstra que estamos a entrar numa nova era da cibersegurança, em que os ataques já conseguem adaptar-se autonomamente. Na DiamWall, identificámos várias tentativas contra os nossos clientes, todas bloqueadas pelo nosso antibot, sem sequer ser necessário recorrer à WAF. É precisamente para enfrentar este tipo de ameaças que continuamos a desenvolver a nossa tecnologia. Orgulho no que estamos a construir e, sobretudo, nos resultados que já conseguimos demonstrar.
🔗 diamwall.com/pt/blog/post/ar… O número de empresas privadas e estatais a serem comprometidas, a sofrer de defacement e web shells não é ao acaso. Por trás de muitos destes ataques está o ARTEX, uma framework que usa inteligência artificial para encontrar falhas, explorá-las e voltar a tentar até conseguir entrar, sem nunca se cansar e com muito pouca intervenção humana. Na DiamWall acompanhamos o ARTEX há cerca de um mês e a nossa threat intelligence não deixa dúvidas: já está a ser usado em Portugal, com muitas entidades comprometidas só nos últimos dias. Foi direcionado a vários dos nossos clientes, diversas vezes, sem qualquer tipo de sucesso, porque o nosso antibot o impediu instantaneamente nos primeiros pedidos, sem que a WAF chegasse sequer a ser necessária. Uma WAF sozinha já não é suficiente, nem mesmo as maiores do mercado, na defesa contra agentes de IA que reescrevem o ataque até encontrarem uma variação que consiga ter sucesso. No nosso blog explicamos o que é o ARTEX, como detetá-lo nos seus logs e o que fazer já esta semana.
There's a new version of this post
222
Ui revolut offline, não estava no meu bingo 😱
We are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers’ money and data are safe. We’ve been working to fix the issue since it was identified this morning and apologise to anyone affected and for any inconvenience caused.
1
27
13,219
Bem-vindo, @JTR_cs ! Ricardo joins us as the new Head Coach of our CS roster. We’re excited to have him on board and can’t wait to see what we can achieve together. Welcome to the team! ❤️ #123FOKUS
9
13
10
150
26,901
The response I got on my ticket 🤡🤡🤡 @FACEITcs @Loza_CS @FACEITSupport @FACEIT @FACEIT_Darwin
6
2
1,474
Time to give this guy a chance as Head Coach!
🧠 LFT | Coach / Assistant Coach | Counter Strike After 2 years competing with FlyQuest, I’m looking for the next opportunity to bring my experience, knowledge, and passion to a team ready to compete at the highest level. 🏆 2 Years of S Tier Tournament Experience 🏅 4 Major Qualifications 📈 Experienced in player development & improvement 📖 Skilled in playbook, strategy & preparation 💪 Extremely dedicated, I grind relentlessly and always look for ways to improve 🗣️ Languages: 🇪🇺 English | | 🇵🇹 Portuguese | 🇪🇸 Spanish I’m hungry to keep grinding and prove myself once again. If you’re looking for a coach who brings experience, preparation, and an unwavering work ethic, my DMs are open. 📩 🔄 RTs are greatly appreciated.
1
7
1,940
Butterfly Emerald #992 0.00077 is on auction. 24h running on CSFloat: csfloat.com/item/97132640371… Inspect URL: steam://run/730//+csgo_econ_action_preview%20E2F2084E26525EE3FA61E6C25AE6CAE4D2E1DA30594A30E1A202E58ACF92EAE3A55A1D Tag ur favorite traders, collectors, thanks! @CorbZcs @AstroooCs @CentraTrades @RaCSGO @RyanTCSGO @Alkem1stCS @RobertB_CSGO RT Appreciated <3
2
7
1,757
Sure, the post-mortem checks out. Retry storms happen, Redis misconfigs happen. None of that explains why the API is held together with tape. 4 versions running in parallel, 20 endpoint calls to load a single page, responses that contradict each other. I've been routing around this for years building extensions thousands of people use. Peak traffic didn't break FACEIT. It just exposed the devs, engineers and architecture behind it.
I wanted to take this opportunity to share some background information on what happened during the FACEIT outages over the last 2 days. My goal here is to provide more information about how the platform responded under record demand. I hope some of you find these insights interesting or can learn something from them for yourselves. I’m trying to bridge the gap between non-technical and technical folks, so some things might be too nuanced for some, while other things might be too high-level for others. On Wednesday, April 22, the amount of traffic to our website far exceeded even our highest forecast, especially so early in the day at 1PM CEST. Like most cloud native software companies, we have more servers provisioned than necessary, including auto-scaling mechanisms to handle traffic spikes. Yet, your enthusiasm for our platform outgrew even these generous buffers, making us push the upper safety auto-scaling threshold. As we recognized the increased traffic, our engineering team started to increase the ceiling of our auto-scaling configuration in terms of physical cloud limits and Kubernetes configuration, practically provisioning more web servers to handle the load. Unfortunately, we had already reached a critical point at which existing servers (Kubernetes Pods, for the techies here) were failing faster than new ones could spawn. What happened in this moment is that the extremely spikey traffic caused people to get errors, making them refresh continuously, which sent our servers into a death spiral that they couldn’t recover from without intervention. As we stabilized the website, the spike in players queuing up led to our Matchmaker falling behind, resulting in much longer than usual queue times. The surge of matches spawning furthermore led to our game server architecture not being able to scale quickly enough. Our game servers are run on so-called bare-metal servers, which are not virtual cloud servers but actual machines, guaranteeing the best performance and latency. Bare-metal machines take longer to provision and deploy into our fleet, and they also sometimes have supply issues. Last week, we put in orders that maxed out available capacity in some of our regions and are waiting on more deliveries. During this period, the fallback is cloud scaling to ensure players are not waiting 10 minutes for a server. However, this scaling mechanism was unable to keep up with the demand. Since Wednesday, we've had additional deliveries, increasing server numbers to an all time high. On Thursday, April 23, as a follow-up to Wednesday's surge, we greatly increased the horizontal scaling of our Matchmaker. However, as we hit peak hours, this extra load pushed our proportionately scaled matchmaking database to its limit. The Matchmaker is using a Redis database, which should be operated in an environment where 20% of memory capacity should be reserved for the system memory, so that it can perform crucial operations like cleaning up stale data while keeping the database performing normally. Given the increased amount of matchmaking capacity, we had to basically double the amount of memory allocated to said database. There was a change made to our configuration files about a year ago that tipped the ratio of Redis and system memory below the 20% threshold. This hidden bottleneck never caused an issue during normal operations, but under the extreme pressure of Season 8's launch and our newly expanded queues, the database stalled. Write requests began timing out, which caused a cascading failure across our game queues. We eventually managed to scale the database up further, while keeping already active matches from cancelling and the platform as a whole operational. The “issue” here is that a zero downtime scaling of such a system basically requires a new replica to spawn and replicate all data from the old instance before connections can be rerouted, which takes time and system resources. Once that scaling safely concluded, we fully restored the service. We are now auditing all of our database configurations to ensure similar resource imbalances are not hiding anywhere else, and reinforced the Matchmaking database with extra system memory headroom.
1
4
827
🤣🤣🤣🤣
Tomara tu jogares como o meu puto @RunahOfficial olha olha, pato!😡
1
3
2,456
Tomara tu jogares como o meu puto @RunahOfficial olha olha, pato!😡
ver o donk a reagir ao Runah não estava no meu bingo de 2026
4
1
96
16,730
Good thing @donk1337 isn't deciding your @FACEIT Elo. Your placement matches do. Season 8 starts April 22.
9
74
7
3,205
201,057
😂 😂
Cloudflare introduces a new tool Check if your site is "Agent Ready" Well per their own vague metrics they got some work to do on their own site :D
2
994
-200€, parecia boa 😂
ATIRARAM UMA MAQUINA DE IQOS AO TCHOUAMENI NA LUZ, EU TOU A CHORAR 😭
3
1,669
Foi exatamente o que eu pensei, ou foi muita "coincidência" ou não sei 😂
Os benfiquistas viram o Tchouameni na ala esquerda e começaram a assobiar porque ele era preto e confundiram com o Vini 😭😭😭😭😭
9
1,637
Human made btw. The entire post.
this shit is going to kill us
3
1,196
Rage bait
if AI can code better than you maybe you suck at coding
1
969
💯
I'm calling this absolute bullshit. Humans behind most of this stuff
1
648