bgpreport

Network · data from 2026-11-12

AS24724 ATMAN

Registry name: ATMAN-Foreign-AS Atman Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24724, 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.
193.111.37.0/24 Valid RIR databaseRIPE 673 100% 66
193.111.38.0/24 Valid RIR databaseRIPE 673 100% 66
212.91.8.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS24724: RIPE::AS24724:AS-FOREIGN. 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 (AS24724 isn't in the set, or no route object for AS24724 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 objectsAS24724 in itNot covered
RIPE::AS24724:AS-FOREIGN RIPElists itself further down9 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-AS21868, AS-HELIACAL, AS-LASNET, AS-SERV … 62511811,178 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 9 are in fix.csv.

  • AS-SET: missing member9
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS-17290:AS-AUSTIN-HADLEY; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS-AS21868; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS-HELIACAL; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS-LASNET; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS-SERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS-STEFAN; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS24724:AS-FOREIGNAS24724:AS-FOREIGN (RIPE) lists AS271200:AS-TECNETBRASIL; no IRR database read has it.

Route objects not announced

Every route object with origin AS24724 is announced.

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.