bgpreport

Network · data from 2026-11-12

AS62178 Master_IT_Technologies MASTER IT Technologies, a.s.

Registry name: Master_IT_Technologies MASTER IT Technologies, a.s., CZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62178, 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.
94.229.92.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.229.93.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.229.80.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.81.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.82.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.86.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.87.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.88.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.90.0/24 Valid RIR databaseRIPE 671 100% 67
94.229.91.0/24 Valid RIR databaseRIPE 671 100% 67
2a05:2c0::/34 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: origin2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin94.229.92.0/24ROAs covering it name AS219062, not AS62178. If AS62178 should announce it, add a ROA for AS62178.2 of 673
Route object: none94.229.92.0/24Route objects for it name AS219062. Add a route object with origin AS62178 in the RIR database for the space.2 of 673
ROA: origin94.229.93.0/24ROAs covering it name AS219062, not AS62178. If AS62178 should announce it, add a ROA for AS62178.2 of 673
Route object: none94.229.93.0/24Route objects for it name AS219062. Add a route object with origin AS62178 in the RIR database for the space.2 of 673

Route objects not announced

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

94.229.83.0/24RIPEValid
185.158.64.0/22RIPEInvalid: 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.