Pascal Stattmann trading as Nodescrape is a public intelligence profile built from public registry, operator, and source material. It summarizes what can be verified about the subject, separates public infrastructure facts from private relationship claims, and keeps contact handling behind the appropriate membership tier. The profile should be read as a monitoring baseline future events, not as a claim that every relationship or dependency is already proven.
The subject operates publicly as Nodescrape, a Germany-linked hosting provider advertising game and KVM servers while maintaining RIPE-visible AS212057 routing, PeeringDB metadata, and an open peering policy. Its role is that of a small network operator with observable registry and routing surfaces whose commercial scale remains self-published but unverified.
BTW tracks this operator because the coupling of a customer-facing hosting storefront with BGP-visible infrastructure creates operational dependencies: changes in route origination, upstreams, peering, or prefix reputation directly affect reachability and filtering for Nodescrape-hosted services, making it a useful network-watchlist item.
BTW tracks this operator because the coupling of a customer-facing hosting storefront with BGP-visible infrastructure creates operational dependencies: changes in route origination, upstreams, peering, or prefix reputation directly affect reachability and filtering for Nodescrape-hosted services, making it a useful network-watchlist item.
The subject operates publicly as Nodescrape, a Germany-linked hosting provider advertising game and KVM servers while maintaining RIPE-visible AS212057 routing, PeeringDB metadata, and an open peering policy. Its role is that of a small network operator with observable registry and routing surfaces whose commercial scale remains self-published but unverified.
If AS212057 changes its upstreams, loses peering, mismanages IRR objects, or sees prefix-level blocklisting, traffic to Nodescrape-hosted workloads could be dropped or deprioritised. Abuse signals such as Tor-exit listings on associated IPs compound reputation risk regardless of operator intent.
Pascal Stattmann trading as Nodescrape is a public intelligence profile built from public registry, operator, and source material. It summarizes what can be verified about the subject, separates public infrastructure facts from private relationship claims, and keeps contact handling behind the appropriate membership tier. The profile should be read as a monitoring baseline future events, not as a claim that every relationship or dependency is already proven.
If AS212057 changes its upstreams, loses peering, mismanages IRR objects, or sees prefix-level blocklisting, traffic to Nodescrape-hosted workloads could be dropped or deprioritised. Abuse signals such as Tor-exit listings on associated IPs compound reputation risk regardless of operator intent.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
Pascal Stattmann trading as Nodescrape
Pascal Stattmann trading as Nodescrape is a German hosting and network infrastructure operator coupling an advertised game and KVM server storefront with autonomous system AS212057. Its routing posture, peering metadata, and prefix reputation create a dependency point for hosted workloads and an intelligence watchlist case for network operators.
Why It Matters
If AS212057 changes its upstreams, loses peering, mismanages IRR objects, or sees prefix-level blocklisting, traffic to Nodescrape-hosted workloads could be dropped or deprioritised. Abuse signals such as Tor-exit listings on associated IPs compound reputation risk regardless of operator intent.
What Public Sources Show
Pascal Stattmann trading as Nodescrape is a Germany-linked hosting and network operator whose advertised game and KVM server storefront is directly coupled to autonomous system AS212057, making its routing posture, peering decisions, and prefix reputation operationally consequential for any network that peers with or filters traffic from Nodescrape-associated address space.
Public registry and PeeringDB records identify the organisation as Nodescrape, also known as Pascal Stattmann, with the long name Pascal Stattmann trading as Nodescrape and network AS212057. The ASN, registered under RIPE on 9 July 2025, is assigned to ORG-NA1616-RIPE and maintained via NODESCRAPE-MNT.
Routing intelligence platforms such as bgp.tools and Cloudflare Radar show active IPv4 and IPv6 prefixes originated from AS212057, including 5.230.5.0/24 and 2a0c:9a40:8860::/44, with upstream visibility through Cogent, RETN and Global Network Management and public peering at GNM-IX.
The operator publishes a customer-facing storefront at nodescrape.net offering premium game hosting and KVM servers, with shopping cart and account registration flows. PeeringDB lists AS212057 with an open peering policy, an IRR as-set (AS212057:AS-NODESCRAPE), a looking-glass at lg-vie-at.nodescra.pe, and self-reported scale metadata of 10 IPv4/10 IPv6 prefixes and 50–100 Gbps traffic. These self-maintained directory fields provide interconnection signals but are not audited scale evidence.
Because the commercial hosting services are directly reachable via AS212057’s BGP announcements, any change in route origination, RPKI or IRR alignment, upstream or exchange relationships, or AS-set maintenance can disrupt connectivity for hosted workloads. Moreover, one of the operator’s IP addresses (85.93.31.31) is listed on AbuseIPDB with a Tor-exit hostname, which, while the provider is not responsible for Tor-user actions, can influence network-level filtering and reputation decisions by other networks.
The public record is sufficient to identify the operator and confirm its routing surface, but business scale remains unverified. The Nodescrape website includes placeholder example.com links and generic testimonial names, and independent confirmation of customer count, revenue, uptime performance, DDoS protection capacity, or datacenter footprint is absent.
The trading name associates the operator with the individual Pascal Stattmann, but separate proof of that person’s operational authority is not publicly established beyond the registry identity context.
Analysts should treat this operator as a live watchlist item. Concrete refresh points include: AS212057 route origination and RPKI/ROA status across route collectors; PeeringDB updates to upstreams, peers, traffic levels, or exchange presence; changes in the AS-set or IRR route objects; any public incident or outage reports linked to Nodescrape services; and migration of its announced prefixes between upstream providers.
Tor-exit or abuse listings on Nodescrape-associated IPs should be monitored as operational reputation signals without being treated as intent evidence.
This profile draws on RIPE RDAP/WHOIS records, PeeringDB organisation and network pages, bgp.tools, Cloudflare Radar, Hurricane Electric’s IRR mirror, the Nodescrape operator website, and AbuseIPDB. All are low-risk official or directory sources, but routing and reputation data require live refresh before action.
Operating Surface
The subject operates publicly as Nodescrape, a Germany-linked hosting provider advertising game and KVM servers while maintaining RIPE-visible AS212057 routing, PeeringDB metadata, and an open peering policy. Its role is that of a small network operator with observable registry and routing surfaces whose commercial scale remains self-published but unverified.
BTW tracks this operator because the coupling of a customer-facing hosting storefront with BGP-visible infrastructure creates operational dependencies: changes in route origination, upstreams, peering, or prefix reputation directly affect reachability and filtering for Nodescrape-hosted services, making it a useful network-watchlist item.
Watchpoints
Nodescrape represents a class of small hosting operators whose BGP-visible infrastructure makes their routing decisions externally consequential. Monitoring AS212057's origination and peering posture provides early warning of reachability or reputation changes that could cascade to downstream hosting customers.
Live BGP observation of AS212057 routes; RPKI/ROA validation status; IRR route-object and AS-set correctness; PeeringDB upstream and exchange changes; any public outage reports; and blocklist or Tor-exit listings on associated prefixes.
Customer count, revenue, deployed-server scale, DDoS-protection capacity, and datacenter footprint are not independently corroborated. Person-specific operational authority is not established beyond trading-name association. Independent verification of hosting service reliability is absent.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for Pascal Stattmann trading as Nodescrape.
- PeeringDB network profile - Lists Nodescrape as an organisation, also known as Pascal Stattmann, with long name Pascal Stattmann trading as Nodescrape and network AS212057.
- PeeringDB network profile - Lists AS212057, Nodescrape website, AS212057:AS-NODESCRAPE, looking glass URL, Europe scope, open peering policy, and GNM-IX operational entry.
- bgp.tools - Shows AS212057 as Pascal Stattmann trading as Nodescrape, active under RIPE, with originated IPv4/IPv6 prefixes, upstreams, peers, and GNM-IX visibility.
- bigdatacloud.com - Lists AS212057 Nodescrape, organisation Pascal Stattmann trading as Nodescrape, registry RIPE, Germany, registered date 2025-07-09, and active prefix data.
- Operator website - Advertises Nodescrape as a premium game-hosting provider and lists KVM servers as a service category with shop/account flows.
- Registry RDAP / WHOIS record - Mirrors RIPE WHOIS/RPSL details for AS212057, ORG-NA1616-RIPE, NODESCRAPE-MNT, and the Nodescrape organisation name.
- bgp.he.net - Lists AS212057:AS-NODESCRAPE as a RIPE AS-set with member AS212057, org ORG-NA1616-RIPE, mnt-by NODESCRAPE-MNT, created 2025-07-09, and last-modified 2025-10-16.
- RIPE registry record - Explains that a RIPE aut-num object contains ASN registration details and also publishes routing policy in the Internet Routing Registry, supporting the control-surface framing for AS212057.
- radar.cloudflare.com - Shows AS212057 routing information under Nodescrape with Germany and nodescrape.net, giving a public observability surface for routing, announced prefixes, connectivity, outages, and anomalies.
- abuseipdb.com - Lists 85.93.31.31 with ASN AS212057, hostname exit1.nodescrape.net and Tor-exit status, while cautioning that the owner or provider is not directly behind Tor-user actions.
- Registry RDAP / WHOIS record - Provides the public RDAP autnum lookup surface for AS212057, supporting registry verification of the Nodescrape autonomous system context when refreshed directly.
Domain of operation
Pascal Stattmann trading as Nodescrape is a German hosting and network infrastructure operator coupling an advertised game and KVM server storefront with autonomous system AS212057. Its routing posture, peering metadata, and prefix reputation create a dependency point for hosted workloads and an intelligence watchlist case for network operators.
- Registry RDAP / WHOIS record: public-source identity and registry context for Pascal Stattmann trading as Nodescrape. Evidence basis: source-49d5ee8d84a6
Timeline
- Pascal Stattmann trading as Nodescrape public evidence observed
BTW tracks this operator because the coupling of a customer-facing hosting storefront with BGP-visible infrastructure creates operational dependencies: changes in route origination, upstreams, peering, or prefix reputation directly affect reachability and filtering for Nodescrape-hosted services, making it a useful network-watchlist item.
At A Glance
- Name: Pascal Stattmann trading as Nodescrape
- Type: Digital infrastructure institution
- Base: Europe
- Profile focus: Institution
What It Does
- business systems
- operator-published service surface
- relationship events
Why It Matters
- If AS212057 changes its upstreams, loses peering, mismanages IRR objects, or sees prefix-level blocklisting, traffic to Nodescrape-hosted workloads could be dropped or deprioritised. Abuse signals such as Tor-exit listings on associated IPs compound reputation risk regardless of operator intent.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
If AS212057 changes its upstreams, loses peering, mismanages IRR objects, or sees prefix-level blocklisting, traffic to Nodescrape-hosted workloads could be dropped or deprioritised. Abuse signals such as Tor-exit listings on associated IPs compound reputation risk regardless of operator intent.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
If AS212057 changes its upstreams, loses peering, mismanages IRR objects, or sees prefix-level blocklisting, traffic to Nodescrape-hosted workloads could be dropped or deprioritised. Abuse signals such as Tor-exit listings on associated IPs compound reputation risk regardless of operator intent.
Watchpoints
- Nodescrape represents a class of small hosting operators whose BGP-visible infrastructure makes their routing decisions externally consequential.
- Monitoring AS212057's origination and peering posture provides early warning of reachability or reputation changes that could cascade to downstream hosting customers.
- Live BGP observation of AS212057 routes; RPKI/ROA validation status; IRR route-object and AS-set correctness; PeeringDB upstream and exchange changes; any public outage reports; and blocklist or Tor-exit listings on associated prefixes.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Pascal Stattmann trading as Nodescrape?
BTW tracks this operator because the coupling of a customer-facing hosting storefront with BGP-visible infrastructure creates operational dependencies: changes in route origination, upstreams, peering, or prefix reputation directly affect reachability and filtering for Nodescrape-hosted services, making it a useful network-watchlist item.
What evidence supports the profile?
public-source identity and registry context for Pascal Stattmann trading as Nodescrape.
What should readers watch next?
Nodescrape represents a class of small hosting operators whose BGP-visible infrastructure makes their routing decisions externally consequential.





