bgpreport

Network · data from 2026-11-12

AS30893 no ack hosting network

Registry name: NOACKHOSTING-AS No ACK Group Holding AB, SE · PeeringDB

11IPv4 routes 90.9% RPKI valid · 100.0% with a route object
6IPv6 routes 100.0% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS30893, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30893, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
192.121.239.0/24 No ROA RIR databaseRIPE 673 100% 67
2a0c:5700:3135::/48 Valid Nonecovered by 2a0c:5700::/29 635 100% 69
2a0c:5700:3136::/48 Valid Nonecovered by 2a0c:5700::/29 635 100% 69
31.22.91.0/24 Valid RIR databaseRIPE 673 100% 67
31.22.92.0/24 Valid RIR databaseRIPE 673 100% 67
193.234.38.0/24 Valid RIR databaseRIPE 672 100% 67
31.22.93.0/24 Valid RIR databaseRIPE 671 100% 67
89.125.12.0/24 Valid RIR databaseRIPE 671 100% 67
153.52.86.0/24 Valid RIR databaseRIPE 671 100% 67
164.138.6.0/24 Valid RIR databaseRIPE 671 100% 67
185.231.100.0/22 Valid RIR databaseRIPE 671 100% 67
195.47.238.0/24 Valid RIR databaseRIPE 671 100% 67
31.22.94.0/24 Valid RIR databaseRIPE 670 100% 66
2a0c:5700:4747::/48 Valid RIR databaseRIPE 636 100% 69
2a0c:5700:3133::/48 Valid RIR databaseRIPE 635 100% 69
2a0c:5700::/29 Valid RIR databaseRIPE 634 100% 69
2a0c:5700:5353::/48 Valid RIR databaseALTDB, RADB, RIPE 610 96% 68

AS-SET

PeeringDB's irr_as_set for AS30893: RIPE::AS-NOACKHOSTING. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS30893 isn't in the set, or no route object for AS30893 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS30893 in itNot covered
RIPE::AS-NOACKHOSTING RIPE2 member sets in no database: AS152135:AS-CSSI, AS199746:AS-NEXTSERV 202548,861 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 7 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • AS-SET: missing member2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none192.121.239.0/24No ROA covers it. Add a ROA for AS30893, maxLength 24.673 of 673
Route object: none2a0c:5700:3135::/48No route object for it. A route object for 2a0c:5700::/29 with origin AS30893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30893 in the RIR database for the space.635 of 636
Route object: none2a0c:5700:3136::/48No route object for it. A route object for 2a0c:5700::/29 with origin AS30893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30893 in the RIR database for the space.635 of 636
AS-SET: missing memberRIPE::AS-NOACKHOSTINGAS-NOACKHOSTING (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NOACKHOSTINGAS-NOACKHOSTING (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

Route objects with origin AS30893 whose prefix no peer sees AS30893 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.84.241.0/24RADBNo ROA
2a01:298:f001::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.