bgpreport

Network · data from 2026-11-12

AS215305 retzor-as Mastersoft S.R.L.

Registry name: retzor-as Mastersoft S.R.L., MD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215305, 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.
5.180.97.0/24 No ROA RIR databaseRIPE 673 100% 67
45.81.35.0/24 No ROA RIR databaseRIPE 671 100% 67
103.112.70.0/23 Valid Other IRR onlyRADB 673 100% 67
87.251.72.0/24 Valid RIR databaseRIPE 673 100% 67
103.112.68.0/23 Valid RIR databaseAPNIC 673 100% 67
103.119.18.0/23 Valid RIR databaseAPNIC 673 100% 67
109.248.42.0/24 Valid RIR databaseRIPE 673 100% 67
144.48.10.0/24 Valid RIR databaseRIPE 673 100% 67
185.245.40.0/24 Valid RIR databaseRIPE 673 100% 67
188.130.208.0/24 Valid RIR databaseRIPE 673 100% 67
192.145.98.0/24 Valid RIR databaseRIPE 673 100% 67
195.78.49.0/24 Valid RIR databaseRIPE 673 100% 67
45.151.180.0/24 Valid RIR databaseRIPE 672 100% 67
45.151.183.0/24 Valid RIR databaseRIPE 672 100% 67
46.8.112.0/24 Valid RIR databaseRIPE 672 100% 67
46.8.113.0/24 Valid RIR databaseRIPE 672 100% 67
80.66.69.0/24 Valid RIR databaseRIPE 672 100% 67
103.118.208.0/23 Valid RIR databaseAPNIC 672 100% 67
103.118.211.0/24 Valid RIR databaseAPNIC 672 100% 67
103.118.210.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.200.28.0/24 Valid RIR databaseRIPE 664 99% 67

AS-SET

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

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none5.180.97.0/24No ROA covers it. Add a ROA for AS215305, maxLength 24.673 of 673
ROA: none45.81.35.0/24No ROA covers it. Add a ROA for AS215305, maxLength 24.671 of 673
Route object: RIR103.112.70.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

5.180.99.0/24RIPENo ROA
69.91.158.0/24ARINValid
103.118.208.0/22APNIC, RADBValid
103.118.208.0/24APNICValid
103.118.209.0/24APNICValid
103.118.210.0/23APNIC, RADBValid
103.200.29.0/24RIPENo ROA
2a13:3d81::/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.