Exposure archiveScreenshots, statements, and reported conduct involving ATBP Hosting and SRVL.October 2026 report
ATBP Hosting ExposedDocumenting reported conduct View the case
Why this site exists

ATBP Hosting & SRVL Exposed.

This website exists to expose the conduct attributed to ATBP Hosting and SRVL: hostile public claims, DDoS-related messages, pressure on providers, customer-targeting behavior, and repeated incidents reported by SereinHost. The October 19 log summary now documents six suspicious panel route patterns, but does not identify who sent the requests.

The goal is direct public accountability. Where screenshots show troubling language, we say so plainly. Where the evidence does not conclusively prove who carried out an attack, we say that plainly too. In particular, the October 19 panel attacker was not identified by the source statement.

First reports: 2025 Updated: October 20, 2026
Submitted screenshot of a January 27 Discord message discussing a hosting provider and a VPS rental
From the evidence archive · January 27, 2026

A screenshot submitted for this archive. The account attribution and full context have not been independently authenticated.

Read source context →
—Records
—Images
—Last updated
Purpose

Expose the pattern. Let the evidence speak.

This site was made to directly call attention to the behavior reported around ATBP Hosting and its named representative SRVL. The archive gathers screenshots, public statements, and timelines pointing to a pattern of false claims, pressure tactics, hostile conduct, and DDoS-related discussions directed at SereinHost. Small hosts should not be attacked, pressured, or undermined behind the scenes.

CLEARLY VISIBLE IN THE SUBMITTED SCREENSHOTSSeptember 2025 DDoS-related conversation; January 2026 message about paying to stop a VPS rental; March account-activity screenshots.
IMPORTANT LIMITThe screenshots do not by themselves prove that every discussed act was carried out, nor do they identify who sent the October 19–20, 2026 HTTP flood.
Main exhibits

What people should see for themselves.

The record contains direct quotes and screenshots tied to the dispute around ATBP Hosting and SRVL. These are the exhibits most central to why this website exists.

Provider discussion

January 27, 2026

A message urging a provider not to rent to a rival

“Nuke their service out of existence, I'll pay for it instead … you don't even need to provide the vps, just don't rent to this guy ever”

A supplied screenshot attributed to the Discord account “! srvl” shows this statement. It does not establish whether the proposal was accepted or acted on.

Read the record →
Chat screenshot

September 2, 2025

A DDoS-related chat tied to the dispute

The screenshot shows a proposal to run DDoS attacks and an account labeled “! srvl” replying: “test mo muna kung gagana rin.”

The screenshot raises questions but alone does not verify payment, an executed attack, or the participants' identities.

Read the record →
Source not identified

October 19–20, 2026

Another reported attack on the SereinHost panel

SereinHost stated its Pterodactyl control panel received an HTTP flood affecting multiple endpoints, reportedly driving CPU usage to 100%.

The October 19 notice confirms a reported disruption—not who carried it out. The earlier screenshots do not establish the identity of this attacker.

Read the record →
OCT 19–20, 2026 / LATEST REPORTED SERVICE DISRUPTION ARCHIVED UPDATE · NOT LIVE

Latest reported incident: another HTTP flood hit the SereinHost panel

SereinHost said different Pterodactyl endpoints were targeted, panel CPU usage reached 100%, and customers experienced interruptions. It also said, “We can't confirm who's behind today's attacks.” The new log summary lists six suspicious request patterns, including 9,505 registration requests in a 10,000-request sample and 19,788 resource requests in a separate 20,000-request sample. Earlier ATBP/SRVL-related screenshots explain this publisher’s concern, but do not identify the October attacker.

View request analysis →
October 19, 2026 · Nginx traffic analysis

Six panel routes in the reported flood.

SereinHost's submitted analysis describes repeated requests to its registration and Pterodactyl server API. This is the traffic record behind the October incident claim; it is not proof of the sender's identity.

The concern is serious. The attribution is not settled.

Earlier Discord screenshots attributed to ATBP Hosting/SRVL are why the publisher suspects a connection to the wider dispute. But knowing panel endpoints or sending requests at scale is not unique to one individual or hosting company. Neither the logs nor the SereinHost October 19 announcement establish SRVL as the attacker.

Loading supplied request patterns…

Other routes including / and /api/remote/servers/* appeared in the supplied analysis but were not established as attack targets. The latter is used by legitimate Wings communication.

Open the October incident record for the full context →
Evidence gallery

See the screenshots directly.

Review the submitted images behind the claims, with captions and incident labels.

Loading images…

Loading evidence gallery…

Timeline of reported conduct

The full record, in date order.

A chronological record of statements, screenshots, reports of attacks, and disputes involving ATBP Hosting, SRVL, and SereinHost. Open any entry for the detailed source notes and evidence.

Loading incident records…

About this archive

Why publish these records?

This site was created to publicly examine allegations and specific messages attributed to SRVL and ATBP Hosting, alongside reports by SereinHost. Proposals to interfere with another host’s server rental, and casual responses to talk of DDoS attacks, deserve scrutiny if accurately attributed. This is an independently published critical archive—not an official SereinHost statement, a forensic finding or proof that a named party carried out the October HTTP flood. Substantive corrections and responses should be considered against the original evidence.

Corrections and contextExamine the actual captures, not personal insults. Do not harass individuals, publish private infrastructure details, or claim the October 2026 attacker has been identified.See SereinHost hardware & plans →
SCREENSHOT VIEWER