bgpreport

Network · data from 2026-11-12

AS201776 Miranda-Media Ltd

Registry name: MIRANDA-AS Miranda-Media Ltd, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201776, 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.

91.201.108.0/22 Invalid: origin RIR databaseRIPE 67 10%low visibility 35
91.201.108.0/23 Invalid: origin RIR databaseRIPE 67 10%low visibility 35
91.201.110.0/23 Invalid: origin RIR databaseRIPE 67 10%low visibility 35
195.3.132.0/23 Invalid: origin RIR databaseRIPE 67 10%low visibility 35
195.3.134.0/23 Invalid: origin RIR databaseRIPE 67 10%low visibility 35
91.201.108.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
91.201.109.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
91.201.110.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
91.201.111.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
193.239.24.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
193.239.25.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
193.239.26.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
193.239.27.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
195.3.134.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
195.3.135.0/24 Invalid: origin RIR databaseRIPE 66 10%low visibility 35
31.40.168.0/23 No ROA RIR databaseRIPE 672 100% 67
31.40.170.0/23 No ROA RIR databaseRIPE 672 100% 67
193.239.24.0/22 No ROA RIR databaseRIPE 672 100% 67
195.3.132.0/22 No ROA RIR databaseRIPE 672 100% 67
2.63.176.0/24 Valid Nonecovered by 2.63.176.0/20 673 100% 67
2.63.180.0/22 Valid Nonecovered by 2.63.176.0/20 673 100% 67
2.63.184.0/24 Valid Nonecovered by 2.63.176.0/20 673 100% 67
2.63.225.0/24 Valid Nonecovered by 2.63.224.0/20 672 100% 67
2.63.231.0/24 Valid Nonecovered by 2.63.224.0/20 672 100% 67
2.63.232.0/24 Valid Nonecovered by 2.63.224.0/20 672 100% 67
31.40.169.0/24 Valid Nonecovered by 31.40.168.0/23 672 100% 67
31.40.170.0/24 Valid Nonecovered by 31.40.170.0/23 672 100% 67
31.40.171.0/24 Valid Nonecovered by 31.40.170.0/23 672 100% 67
31.40.208.0/24 Valid Nonecovered by 31.40.208.0/22 672 100% 67
31.40.209.0/24 Valid Nonecovered by 31.40.208.0/22 672 100% 67
31.40.211.0/24 Valid Nonecovered by 31.40.208.0/22 672 100% 67
77.83.10.0/24 Valid Nonecovered by 77.83.8.0/22 672 100% 67
85.174.150.0/24 Valid Nonecovered by 85.174.144.0/20 672 100% 67
89.107.138.0/23 Valid Nonecovered by 89.107.136.0/22 672 100% 67
94.126.30.0/24 Valid Nonecovered by 94.126.24.0/21 672 100% 67
178.173.126.0/24 Valid Nonecovered by 178.173.124.0/22 672 100% 67
178.173.127.0/24 Valid Nonecovered by 178.173.124.0/22 672 100% 67
2.63.158.0/24 Valid Nonecovered by 2.63.144.0/20 1 0%low visibility 1
2.63.159.0/24 Valid Nonecovered by 2.63.144.0/20 1 0%low visibility 1
2.63.176.0/20 Valid RIR databaseRIPE 673 100% 67
78.31.216.0/24 Valid RIR databaseRIPE 673 100% 67
78.31.217.0/24 Valid RIR databaseRIPE 673 100% 67
78.31.218.0/24 Valid RIR databaseRIPE 673 100% 67
78.31.219.0/24 Valid RIR databaseRIPE 673 100% 67
78.31.220.0/24 Valid RIR databaseRIPE 673 100% 67
78.31.222.0/24 Valid RIR databaseRIPE 673 100% 67
78.31.223.0/24 Valid RIR databaseRIPE 673 100% 67
2.59.51.0/24 Valid RIR databaseRIPE 672 100% 67
2.63.144.0/20 Valid RIR databaseRIPE 672 100% 67
2.63.224.0/20 Valid RIR databaseRIPE 672 100% 67
31.40.130.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.132.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.137.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.138.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.140.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.143.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.151.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.153.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.162.0/23 Valid RIR databaseRIPE 672 100% 67
31.40.165.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.167.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.168.0/24 Valid RIR databaseRIPE 672 100% 67
31.40.172.0/23 Valid RIR databaseRIPE 672 100% 67
31.40.178.0/23 Valid RIR databaseRIPE 672 100% 67
31.40.208.0/22 Valid RIR databaseRIPE 672 100% 67
31.40.252.0/22 Valid RIR databaseRIPE 672 100% 67
37.44.252.0/22 Valid RIR databaseRIPE 672 100% 67
46.61.245.0/24 Valid RIR databaseRIPE 672 100% 67
77.83.8.0/22 Valid RIR databaseRIPE 672 100% 67
77.83.16.0/22 Valid RIR databaseRIPE 672 100% 67
78.31.221.0/24 Valid RIR databaseRIPE 672 100% 67
78.136.196.0/22 Valid RIR databaseRIPE 672 100% 67
78.136.200.0/21 Valid RIR databaseRIPE 672 100% 67
78.153.137.0/24 Valid RIR databaseRIPE 672 100% 67
78.153.138.0/24 Valid RIR databaseRIPE 672 100% 67
78.153.147.0/24 Valid RIR databaseRIPE 672 100% 67
83.171.252.0/22 Valid RIR databaseRIPE 672 100% 67
83.172.60.0/22 Valid RIR databaseRIPE 672 100% 67
83.172.61.0/24 Valid RIR databaseRIPE 672 100% 67
83.172.62.0/24 Valid RIR databaseRIPE 672 100% 67
84.42.92.0/24 Valid RIR databaseRIPE 672 100% 67
84.42.93.0/24 Valid RIR databaseRIPE 672 100% 67
84.42.94.0/24 Valid RIR databaseRIPE 672 100% 67
84.42.95.0/24 Valid RIR databaseRIPE 672 100% 67
85.115.200.0/22 Valid RIR databaseRIPE 672 100% 67
85.174.144.0/20 Valid RIR databaseRIPE 672 100% 67
89.107.136.0/22 Valid RIR databaseRIPE 672 100% 67
91.103.110.0/23 Valid RIR databaseRIPE 672 100% 67
92.118.132.0/24 Valid RIR databaseRIPE 672 100% 67
92.118.133.0/24 Valid RIR databaseRIPE 672 100% 67
92.118.135.0/24 Valid RIR databaseRIPE 672 100% 67
94.126.24.0/21 Valid RIR databaseRIPE 672 100% 67
109.94.220.0/22 Valid RIR databaseRIPE 672 100% 67
109.236.52.0/22 Valid RIR databaseRIPE 672 100% 67
109.237.104.0/24 Valid RIR databaseRIPE 672 100% 67
176.119.169.0/24 Valid RIR databaseRIPE 672 100% 67
176.119.170.0/24 Valid RIR databaseRIPE 672 100% 67
176.119.171.0/24 Valid RIR databaseRIPE 672 100% 67
176.119.172.0/24 Valid RIR databaseRIPE 672 100% 67
176.208.74.0/24 Valid RIR databaseRIPE 672 100% 67
176.211.120.0/22 Valid RIR databaseRIPE 672 100% 67
178.34.152.0/21 Valid RIR databaseRIPE 672 100% 67
178.34.158.0/24 Valid RIR databaseRIPE 672 100% 67
178.34.176.0/20 Valid RIR databaseRIPE 672 100% 67
178.173.124.0/22 Valid RIR databaseRIPE 672 100% 67
185.64.44.0/22 Valid RIR databaseRIPE 672 100% 67
185.116.228.0/23 Valid RIR databaseRIPE 672 100% 67
185.116.230.0/23 Valid RIR databaseRIPE 672 100% 67
188.119.76.0/22 Valid RIR databaseRIPE 672 100% 67
188.124.224.0/21 Valid RIR databaseRIPE 672 100% 67
188.124.248.0/21 Valid RIR databaseRIPE 672 100% 67
193.47.44.0/22 Valid RIR databaseRIPE 672 100% 67
193.56.64.0/22 Valid RIR databaseRIPE 672 100% 67
193.56.72.0/22 Valid RIR databaseRIPE 672 100% 67
193.148.52.0/22 Valid RIR databaseRIPE 672 100% 67
217.197.172.0/22 Valid RIR databaseRIPE 672 100% 67
46.161.9.0/24 Valid RIR databaseRIPE 671 100% 67
2a04:f800::/29 Valid RIR databaseRIPE 634 100% 68
46.61.150.0/24 Valid RIR databaseRIPE 12 2%low visibility 7
188.254.122.0/23 Valid RIR databaseRIPE 12 2%low visibility 7
92.50.204.0/24 Valid RIR databaseRIPE 9 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS201776: AS-MRNDA. 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 (AS201776 isn't in the set, or no route object for AS201776 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 objectsAS201776 in itNot covered
AS-MRNDA RIPElists itself further down9 member sets in no database: AS-CRIS, AS-DONCLIP, AS-DVCOM, AS-HOME-WORD, AS-LEVEL-MSK-NR … 4801453,742 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 74 are in fix.csv.

  • ROA: origin15
  • ROA: none4
  • Route object: none20
  • AS-SET: missing member9
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: origin91.201.108.0/22ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.67 of 673
ROA: origin91.201.108.0/23ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.67 of 673
ROA: origin91.201.110.0/23ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.67 of 673
ROA: origin195.3.132.0/23ROAs covering it name AS12389, AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.67 of 673
ROA: origin195.3.134.0/23ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.67 of 673
ROA: origin91.201.108.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin91.201.109.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin91.201.110.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin91.201.111.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin193.239.24.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin193.239.25.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin193.239.26.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin193.239.27.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin195.3.134.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: origin195.3.135.0/24ROAs covering it name AS29031, not AS201776. If AS201776 should announce it, add a ROA for AS201776.66 of 673
ROA: none31.40.168.0/23No ROA covers it. Add a ROA for AS201776, maxLength 23.672 of 673
ROA: none31.40.170.0/23No ROA covers it. Add a ROA for AS201776, maxLength 23.672 of 673
ROA: none193.239.24.0/22No ROA covers it. Add a ROA for AS201776, maxLength 22.672 of 673
ROA: none195.3.132.0/22No ROA covers it. Add a ROA for AS201776, maxLength 22.672 of 673
Route object: none2.63.176.0/24No route object for it. A route object for 2.63.176.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.673 of 673
Route object: none2.63.180.0/22No route object for it. A route object for 2.63.176.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.673 of 673
Route object: none2.63.184.0/24No route object for it. A route object for 2.63.176.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.673 of 673
Route object: none2.63.225.0/24No route object for it. A route object for 2.63.224.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none2.63.231.0/24No route object for it. A route object for 2.63.224.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none2.63.232.0/24No route object for it. A route object for 2.63.224.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none31.40.169.0/24No route object for it. A route object for 31.40.168.0/23 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none31.40.170.0/24No route object for it. A route object for 31.40.170.0/23 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none31.40.171.0/24No route object for it. A route object for 31.40.170.0/23 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none31.40.208.0/24No route object for it. A route object for 31.40.208.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none31.40.209.0/24No route object for it. A route object for 31.40.208.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none31.40.211.0/24No route object for it. A route object for 31.40.208.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none77.83.10.0/24No route object for it. A route object for 77.83.8.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none85.174.150.0/24No route object for it. A route object for 85.174.144.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none89.107.138.0/23No route object for it. A route object for 89.107.136.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none94.126.30.0/24No route object for it. A route object for 94.126.24.0/21 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none178.173.126.0/24No route object for it. A route object for 178.173.124.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none178.173.127.0/24No route object for it. A route object for 178.173.124.0/22 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.672 of 673
Route object: none2.63.158.0/24No route object for it. A route object for 2.63.144.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.1 of 673
Route object: none2.63.159.0/24No route object for it. A route object for 2.63.144.0/20 with origin AS201776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201776 in the RIR database for the space.1 of 673
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-CRIS; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-DONCLIP; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-DVCOM; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-HOME-WORD; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-LEVEL-MSK-NR; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-MOLS; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-MULTSYS; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-SVCOM; no IRR database read has it.
AS-SET: missing memberAS-MRNDAAS-MRNDA (RIPE) lists AS-WINTELECOM; no IRR database read has it.

Route objects not announced

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

31.40.139.0/24RIPENo ROA
31.40.141.0/24RIPENo ROA
31.40.174.0/24RIPEValid
46.151.146.0/23RIPEInvalid: origin
46.151.148.0/23RIPEInvalid: origin
89.107.138.0/24RIPEValid
89.107.139.0/24RIPEValid
91.103.110.0/24RIPEInvalid: maxLength
92.50.204.0/23RIPEValid
92.50.205.0/24RIPEValid
94.25.87.0/24RIPEValid
94.231.216.0/22RIPENo ROA
178.34.159.0/24RIPEInvalid: maxLength
178.34.180.0/24RIPEInvalid: maxLength
178.34.191.0/24RIPEInvalid: maxLength
185.207.252.0/23RIPENo ROA
185.207.254.0/23RIPENo ROA
188.124.230.0/24RIPEInvalid: maxLength
188.128.76.0/23RIPEValid
188.128.76.0/24RIPEValid
188.128.77.0/24RIPEValid
188.254.122.0/24RIPEValid
188.254.123.0/24RIPEValid
195.3.132.0/24RIPEInvalid: origin
195.3.133.0/24RIPEInvalid: origin
195.69.200.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.