bgpreport

Network · data from 2026-11-12

AS42841 ANTIK Telecom

Registry name: ANTIK ANTIK Telecom s.r.o, SK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42841, 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.
88.212.0.0/20 Valid Nonecovered by 88.212.0.0/19 279 41% 58
88.212.16.0/20 Valid Nonecovered by 88.212.0.0/19 279 41% 58
88.212.32.0/20 Valid Nonecovered by 88.212.32.0/19 279 41% 58
88.212.48.0/20 Valid Nonecovered by 88.212.32.0/19 279 41% 58
88.212.0.0/18 Valid RIR databaseRIPE 673 100% 67
185.61.16.0/22 Valid RIR databaseRIPE 673 100% 66
2a02:130::/32 Valid RIR databaseRIPE 636 100% 69
88.212.0.0/19 Valid RIR databaseRIPE 454 67% 63
88.212.32.0/19 Valid RIR databaseRIPE 454 67% 63

AS-SET

PeeringDB's irr_as_set for AS42841: RIPE::AS-ANTIK. 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 (AS42841 isn't in the set, or no route object for AS42841 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 objectsAS42841 in itNot covered
RIPE::AS-ANTIK RIPE 21218 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 4 are in fix.csv.

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none88.212.0.0/20No route object for it. A route object for 88.212.0.0/19 with origin AS42841 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42841 in the RIR database for the space.279 of 673
Route object: none88.212.16.0/20No route object for it. A route object for 88.212.0.0/19 with origin AS42841 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42841 in the RIR database for the space.279 of 673
Route object: none88.212.32.0/20No route object for it. A route object for 88.212.32.0/19 with origin AS42841 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42841 in the RIR database for the space.279 of 673
Route object: none88.212.48.0/20No route object for it. A route object for 88.212.32.0/19 with origin AS42841 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42841 in the RIR database for the space.279 of 673

Route objects not announced

Every route object with origin AS42841 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.