bgpreport

Network · data from 2026-11-12

AS208143 amccomp-unin mapnet IT services s.r.o.

Registry name: amccomp-unin mapnet IT services s.r.o., CZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208143, 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.
2a02:6c20:828::/48 Valid None 635 100% 67
185.179.34.0/24 Valid RIR databaseRIPE 673 100% 67
2a02:6c20:5::/48 Valid RIR databaseRIPE 636 100% 67
2a02:6c20:810::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS208143 isn't in PeeringDB, where networks name their AS-SET.

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 3 are in fix.csv.

  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2a02:6c20:828::/48No route object for it. Add a route object with origin AS208143 in the RIR database for the space.635 of 636

Route objects not announced

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

185.179.32.0/24RIPEInvalid: origin
185.179.33.0/24RIPEInvalid: origin

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.