bgpreport

Network · data from 2026-11-12

AS62000 moji-netrix edge network

Registry name: AS62000 SERVERD SAS, FR · PeeringDB

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

Announced routes

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

89.234.180.0/24 No ROA Nonecovered by 89.234.180.0/22 1 0%low visibility 1
89.234.181.0/24 No ROA Nonecovered by 89.234.180.0/22 1 0%low visibility 1
89.234.182.0/24 No ROA Nonecovered by 89.234.180.0/22 1 0%low visibility 1
89.234.183.0/24 No ROA Nonecovered by 89.234.180.0/22 1 0%low visibility 1
185.0.19.0/24 No ROA None 1 0%low visibility 1
89.234.180.0/22 No ROA RIR databaseRIPE 671 100% 66
93.127.158.0/24 Valid Nonecovered by 93.127.158.0/23 672 100% 66
2a09:6387:b00b::/48 Valid Nonecovered by 2a09:6380::/29 633 100% 67
2a09:6386::/32 Valid Nonecovered by 2a09:6380::/29 632 99% 67
2a09:6385:1::/48 Valid Nonecovered by 2a09:6385::/32 7 1%low visibility 6
193.168.144.0/24 Valid RIR databaseRIPE 673 100% 67
185.216.25.0/24 Valid RIR databaseRIPE 672 100% 66
185.216.26.0/24 Valid RIR databaseRIPE 672 100% 66
193.168.145.0/24 Valid RIR databaseRIPE 672 100% 66
193.168.146.0/24 Valid RIR databaseRIPE 672 100% 66
193.168.147.0/24 Valid RIR databaseRIPE 672 100% 66
195.246.112.0/24 Valid RIR databaseRIPE 672 100% 66
45.112.121.0/24 Valid RIR databaseRIPE 671 100% 67
45.147.96.0/23 Valid RIR databaseRIPE 671 100% 66
45.155.168.0/22 Valid RIR databaseRIPE 671 100% 66
82.26.68.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
185.157.244.0/24 Valid RIR databaseRIPE 671 100% 66
185.157.245.0/24 Valid RIR databaseRIPE 671 100% 66
185.216.24.0/24 Valid RIR databaseRIPE 671 100% 66
185.216.27.0/24 Valid RIR databaseRIPE 671 100% 66
45.147.98.0/24 Valid RIR databaseRIPE 670 100% 66
45.147.99.0/24 Valid RIR databaseRIPE 670 100% 66
45.155.168.0/24 Valid RIR databaseRIPE 670 100% 66
46.203.90.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
2a09:6382::/32 Valid RIR databaseRIPE 633 100% 67
2a09:6383::/32 Valid RIR databaseRIPE 633 100% 67
2a09:6385::/32 Valid RIR databaseRIPE 633 100% 67
2a07:abc0::/29 Valid RIR databaseRIPE 632 99% 67
2a0b:b140::/29 Valid RIR databaseRIPE 632 99% 67
2a09:6384::/32 Valid RIR databaseRIPE 605 95% 67

AS-SET

PeeringDB's irr_as_set for AS62000: RIPE::AS-NETRIX. 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 (AS62000 isn't in the set, or no route object for AS62000 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 objectsAS62000 in itNot covered
RIPE::AS-NETRIX RIPElists itself further down11 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-NIXCON, AS-PIXOOF, AS-PLAINELIMAGNE, AS-SERV … 5561557,271 Yes 1

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

  • ROA: none6
  • Route object: none9
  • AS-SET: missing member11
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none89.234.180.0/24No ROA covers it. Add a ROA for AS62000, maxLength 24.1 of 673
Route object: none89.234.180.0/24No route object for it. A route object for 89.234.180.0/22 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.1 of 673
ROA: none89.234.181.0/24No ROA covers it. Add a ROA for AS62000, maxLength 24.1 of 673
Route object: none89.234.181.0/24No route object for it. A route object for 89.234.180.0/22 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.1 of 673
ROA: none89.234.182.0/24No ROA covers it. Add a ROA for AS62000, maxLength 24.1 of 673
Route object: none89.234.182.0/24No route object for it. A route object for 89.234.180.0/22 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.1 of 673
ROA: none89.234.183.0/24No ROA covers it. Add a ROA for AS62000, maxLength 24.1 of 673
Route object: none89.234.183.0/24No route object for it. A route object for 89.234.180.0/22 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.1 of 673
ROA: none185.0.19.0/24No ROA covers it. Add a ROA for AS62000, maxLength 24.1 of 673
Route object: none185.0.19.0/24No route object for it. Add a route object with origin AS62000 in the RIR database for the space.1 of 673
ROA: none89.234.180.0/22No ROA covers it. Add a ROA for AS62000, maxLength 22.671 of 673
Route object: none93.127.158.0/24No route object for it. A route object for 93.127.158.0/23 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.672 of 673
Route object: none2a09:6387:b00b::/48No route object for it. A route object for 2a09:6380::/29 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.633 of 636
Route object: none2a09:6386::/32No route object for it. A route object for 2a09:6380::/29 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.632 of 636
Route object: none2a09:6385:1::/48No route object for it. A route object for 2a09:6385::/32 with origin AS62000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62000 in the RIR database for the space.7 of 636
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS-17290:AS-AUSTIN-HADLEY; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS-NIXCON; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS-PIXOOF; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS-PLAINELIMAGNE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS-SERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS-STEFAN; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS152135:AS-CSSI; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS18002:AS-WORLDPHONE-IN; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS214625:AS-FIBER64; no IRR database read has it.
AS-SET: missing memberRIPE::AS-NETRIXAS-NETRIX (RIPE) lists AS401066:AS-LOWPINGLLC; no IRR database read has it.

Route objects not announced

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

45.147.96.0/22RIPENo ROA
45.147.96.0/24RIPEValid
45.147.97.0/24RIPEValid
45.155.169.0/24RIPEValid
45.155.170.0/24RIPEValid
45.155.171.0/24RIPEValid
91.197.5.0/24RIPEInvalid: origin
91.197.6.0/24RIPEInvalid: origin
93.127.158.0/23RADB, RIPEValid
94.231.36.0/23RIPEInvalid: origin
149.91.88.0/22RIPE-NONAUTHNo ROA
154.49.211.0/24RIPE-NONAUTHNo ROA
154.49.212.0/23RIPE-NONAUTHNo ROA
154.49.248.0/22RADBNo ROA
154.49.248.0/23RADBNo ROA
154.49.250.0/23RADBNo ROA
185.32.70.0/24RIPEInvalid: origin
185.103.140.0/24RIPEInvalid: origin
185.157.244.0/23RIPENo ROA
185.163.124.0/22RIPEValid
185.207.226.0/24RIPEInvalid: origin
185.216.24.0/22RIPENo ROA
193.168.144.0/22RIPENo ROA
193.168.146.0/23RIPENo ROA
194.146.126.0/24RIPEInvalid: origin
194.147.47.0/24RIPEInvalid: origin
194.147.67.0/24RIPEInvalid: origin
2a07:abc3::/33RIPEValid
2a07:abc3:8000::/33RIPEValid
2a07:abc4::/33RIPEValid
2a07:abc4:8000::/33RIPEValid
2a09:6380::/29RIPENo ROA
2a09:6381::/32RIPENo ROA
2a0b:b800::/29RIPEInvalid: 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.