bgpreport

Network · data from 2026-11-12

AS57218 RighTel "Rightel Communication Service Company PJS"

Registry name: RighTel "Rightel Communication Service Company PJS", IR · not in PeeringDB

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

Announced routes

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

95.162.176.0/21 Valid Nonecovered by 95.162.176.0/20 672 100% 66
37.137.96.0/19 Valid Nonecovered by 37.137.64.0/18 671 100% 67
5.62.192.0/24 Valid RIR databaseRIPE 672 100% 66
5.62.193.0/24 Valid RIR databaseRIPE 672 100% 66
5.62.194.0/23 Valid RIR databaseRIPE 672 100% 66
5.62.196.0/22 Valid RIR databaseRIPE 672 100% 66
5.62.200.0/21 Valid RIR databaseRIPE 672 100% 66
5.62.208.0/20 Valid RIR databaseRIPE 672 100% 66
5.62.224.0/19 Valid RIR databaseRIPE 672 100% 66
5.72.0.0/19 Valid RIR databaseRIPE 672 100% 66
5.134.128.0/18 Valid RIR databaseRIPE 672 100% 66
5.134.136.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.152.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.156.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.160.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.164.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.168.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.172.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.176.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.180.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.184.0/22 Valid RIR databaseRIPE 672 100% 66
5.134.191.0/24 Valid RIR databaseRIPE 672 100% 66
5.200.96.0/19 Valid RIR databaseRIPE 672 100% 66
37.44.56.0/21 Valid RIR databaseRIPE 672 100% 67
37.137.0.0/19 Valid RIR databaseRIPE 672 100% 67
37.137.40.0/21 Valid RIR databaseRIPE 672 100% 67
37.153.176.0/20 Valid RIR databaseRIPE 672 100% 67
37.156.48.0/20 Valid RIR databaseRIPE 672 100% 67
37.156.152.0/21 Valid RIR databaseRIPE 672 100% 67
89.32.96.0/20 Valid RIR databaseRIPE 672 100% 67
89.34.32.0/24 Valid RIR databaseRIPE 672 100% 67
89.34.33.0/24 Valid RIR databaseRIPE 672 100% 67
89.34.34.0/23 Valid RIR databaseRIPE 672 100% 67
89.34.36.0/22 Valid RIR databaseRIPE 672 100% 67
89.34.48.0/20 Valid RIR databaseRIPE 672 100% 67
91.229.214.0/23 Valid RIR databaseRIPE 672 100% 66
94.24.80.0/20 Valid RIR databaseRIPE 672 100% 67
95.162.0.0/17 Valid RIR databaseRIPE 672 100% 66
95.162.128.0/17 Valid RIR databaseRIPE 672 100% 66
95.162.224.0/20 Valid RIR databaseRIPE 672 100% 66
185.24.136.0/24 Valid RIR databaseRIPE 672 100% 66
188.214.6.0/24 Valid RIR databaseRIPE 672 100% 66
188.214.84.0/22 Valid RIR databaseRIPE 672 100% 66
188.215.24.0/22 Valid RIR databaseRIPE 672 100% 66
188.215.88.0/22 Valid RIR databaseRIPE 672 100% 66
213.195.38.0/23 Valid RIR databaseRIPE 672 100% 66
213.195.40.0/21 Valid RIR databaseRIPE 672 100% 66
37.137.36.0/24 Valid RIR databaseRIPE 671 100% 67
37.137.48.0/20 Valid RIR databaseRIPE 671 100% 67
37.137.128.0/17 Valid RIR databaseRIPE 671 100% 67
77.81.192.0/20 Valid RIR databaseRIPE 671 100% 67
77.81.208.0/20 Valid RIR databaseRIPE 671 100% 67
89.32.0.0/19 Valid RIR databaseRIPE 671 100% 67
89.34.40.0/21 Valid RIR databaseRIPE 671 100% 67
89.34.128.0/19 Valid RIR databaseRADB, RIPE 671 100% 67
89.41.192.0/19 Valid RIR databaseRIPE 671 100% 67
89.47.64.0/21 Valid RIR databaseRIPE 671 100% 67
89.47.72.0/21 Valid RIR databaseRIPE 671 100% 67
89.47.128.0/19 Valid RIR databaseRIPE 671 100% 67
93.114.16.0/20 Valid RIR databaseRIPE 671 100% 67
94.24.16.0/21 Valid RIR databaseRIPE 671 100% 67
94.24.96.0/21 Valid RIR databaseRIPE 671 100% 67
188.208.64.0/19 Valid RIR databaseRIPE 671 100% 67
188.208.144.0/20 Valid RIR databaseRIPE 671 100% 67
188.208.156.0/24 Valid RIR databaseRIPE 671 100% 67
188.208.158.0/23 Valid RIR databaseRIPE 671 100% 67
188.208.224.0/19 Valid RIR databaseRIPE 671 100% 67
37.137.32.0/22 Valid RIR databaseRIPE 670 100% 67
188.208.157.0/24 Valid RIR databaseRIPE 670 100% 67
188.208.160.0/20 Valid RIR databaseRIPE 670 100% 67
188.208.176.0/20 Valid RIR databaseRIPE 670 100% 67
188.214.4.0/23 Valid RIR databaseRIPE 670 100% 67
188.214.7.0/24 Valid RIR databaseRIPE 670 100% 67
213.195.32.0/22 Valid RIR databaseRIPE 670 100% 67
213.195.36.0/23 Valid RIR databaseRIPE 670 100% 67
37.137.38.0/23 Valid RIR databaseRIPE 666 99% 67
2a03:ef42::/34 Valid RIR databaseRIPE 635 100% 67
2a03:ef42:4000::/34 Valid RIR databaseRIPE 635 100% 67
2a03:ef42:8000::/34 Valid RIR databaseRIPE 635 100% 67
2a03:ef42:c000::/34 Valid RIR databaseRIPE 635 100% 67
2a03:ef43::/34 Valid RIR databaseRIPE 635 100% 67
2a03:ef43::/43 Valid RIR databaseRIPE 635 100% 67
2a03:ef43:3::/48 Valid RIR databaseRIPE 635 100% 67
2a03:ef43:c000::/48 Valid RIR databaseRIPE 635 100% 67
2a03:ef44::/34 Valid RIR databaseRIPE 635 100% 67
95.162.32.0/19 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • Route object: none2
  • Route object: not announced152
ChangePrefix or setDetailFull-table peers
Route object: none95.162.176.0/21No route object for it. A route object for 95.162.176.0/20 with origin AS57218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57218 in the RIR database for the space.672 of 673
Route object: none37.137.96.0/19No route object for it. A route object for 37.137.64.0/18 with origin AS57218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57218 in the RIR database for the space.671 of 673

Route objects not announced

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

5.62.192.0/18RIPEValid
5.62.192.0/19RIPEValid
5.72.0.0/16RIPEValid
5.72.32.0/19RIPEValid
5.72.64.0/19RIPEValid
5.72.96.0/19RIPEValid
5.72.128.0/19RIPEValid
5.72.160.0/19RIPEValid
5.72.192.0/19RIPEValid
5.72.224.0/19RIPEValid
5.73.0.0/16RIPEValid
5.73.0.0/19RIPEValid
5.73.32.0/19RIPEValid
5.73.64.0/19RIPEValid
5.73.96.0/19RIPEValid
5.73.128.0/19RIPEValid
5.73.160.0/19RIPEValid
5.73.192.0/19RIPEValid
5.73.224.0/19RIPEValid
5.134.128.0/20RIPEValid
5.134.128.0/22RIPEValid
5.134.132.0/22RIPEValid
5.134.140.0/22RIPEValid
5.134.144.0/20RIPEValid
5.134.144.0/22RIPEValid
5.134.148.0/22RIPEValid
5.134.160.0/20RIPEValid
5.134.176.0/20RIPEValid
5.134.188.0/22RIPEInvalid: maxLength
5.200.96.0/20RIPEValid
5.200.112.0/20RIPEValid
37.44.56.0/22RIPEValid
37.44.56.0/24RIPEInvalid: maxLength
37.44.60.0/22RIPEValid
37.137.0.0/17RIPEValid
37.137.0.0/18RIPEValid
37.137.64.0/18RIPEValid
37.137.128.0/18RIPEValid
37.137.192.0/18RIPEValid
37.153.176.0/21RIPEValid
37.153.184.0/21RIPEValid
37.156.48.0/21RIPEValid
37.156.56.0/21RIPEValid
37.156.152.0/22RIPEValid
37.156.156.0/22RIPEValid
77.81.192.0/19RIPEValid
89.32.0.0/20RIPEValid
89.32.16.0/20RIPEValid
89.32.96.0/21RIPEValid
89.32.104.0/21RIPEValid
89.34.32.0/19RIPEValid
89.34.32.0/20RIPEValid
89.34.32.0/23RIPEValid
89.34.128.0/20RIPEValid
89.34.144.0/20RIPEValid
89.41.192.0/20RIPEValid
89.41.208.0/20RIPEValid
89.47.64.0/20RIPEValid
89.47.72.0/23RIPEInvalid: maxLength
89.47.128.0/20RIPEValid
89.47.128.0/24RIPEInvalid: maxLength
89.47.144.0/20RIPEValid
91.229.214.0/24RIPEValid
91.229.215.0/24RIPEValid
92.114.64.0/20RIPEValid
92.114.64.0/21RIPEValid
92.114.72.0/21RIPEValid
93.114.16.0/21RIPEValid
93.114.24.0/21RIPEValid
94.24.0.0/20RIPEValid
94.24.0.0/21RIPEValid
94.24.8.0/21RIPEValid
94.24.16.0/22RIPEValid
94.24.20.0/22RIPEValid
94.24.80.0/21RIPEValid
94.24.88.0/21RIPEValid
94.24.96.0/22RIPEValid
94.24.100.0/22RIPEValid
95.162.0.0/16RIPEValid
95.162.0.0/19RIPEValid
95.162.0.0/20RIPEValid
95.162.16.0/20RIPEValid
95.162.32.0/20RIPEValid
95.162.48.0/20RIPEValid
95.162.64.0/19RIPEValid
95.162.64.0/20RIPEValid
95.162.80.0/20RIPEValid
95.162.96.0/19RIPEValid
95.162.96.0/20RIPEValid
95.162.112.0/20RIPEValid
95.162.128.0/19RIPEValid
95.162.128.0/20RIPEValid
95.162.144.0/20RIPEValid
95.162.160.0/19RIPEValid
95.162.160.0/20RIPEValid
95.162.176.0/20RIPEValid
95.162.192.0/19RIPEValid
95.162.192.0/20RIPEValid
95.162.208.0/20RIPEValid
95.162.224.0/19RIPEValid
95.162.240.0/20RIPEValid
95.162.248.0/24RIPEValid
185.24.136.0/23RIPEValid
185.24.137.0/24RIPEValid
185.24.228.0/22RIPEValid
185.24.228.0/23RIPEValid
185.24.230.0/23RIPEValid
188.208.64.0/20RIPEValid
188.208.80.0/20RIPEValid
188.208.144.0/21RIPEValid
188.208.152.0/21RIPEValid
188.208.160.0/19RIPEValid
188.208.224.0/20RIPEValid
188.208.224.0/24RIPEInvalid: maxLength
188.208.240.0/20RIPEValid
188.208.243.0/24RIPEValid
188.214.4.0/22RIPEValid
188.214.6.0/23RIPEValid
188.214.84.0/23RIPEValid
188.214.86.0/23RIPEValid
188.215.24.0/23RIPEValid
188.215.26.0/23RIPEValid
188.215.88.0/23RIPEValid
188.215.90.0/23RIPEValid
213.195.32.0/20RIPEValid
213.195.32.0/21RIPEValid
213.195.38.0/24RIPEInvalid: maxLength
213.195.48.0/22RIPEValid
213.195.48.0/23RIPEValid
213.195.50.0/23RIPEValid
2a03:ef40::/29RIPENo ROA
2a03:ef40::/30RIPENo ROA
2a03:ef40::/32RIPENo ROA
2a03:ef42::/32RIPENo ROA
2a03:ef42::/64RIPEInvalid: maxLength
2a03:ef42:0:1::/64RIPEInvalid: maxLength
2a03:ef42:c004::/49RIPEInvalid: maxLength
2a03:ef42:c004:8000::/49RIPEInvalid: maxLength
2a03:ef42:c005::/49RIPEInvalid: maxLength
2a03:ef42:c005:8000::/49RIPEInvalid: maxLength
2a03:ef42:c006::/49RIPEInvalid: maxLength
2a03:ef42:c006:8000::/49RIPEInvalid: maxLength
2a03:ef42:c007::/49RIPEInvalid: maxLength
2a03:ef42:c007:8000::/49RIPEInvalid: maxLength
2a03:ef42:c008::/49RIPEInvalid: maxLength
2a03:ef42:c008:8000::/49RIPEInvalid: maxLength
2a03:ef43::/32RIPENo ROA
2a03:ef44::/30RIPENo ROA
2a03:ef44::/32RIPENo ROA
2a03:ef45::/32RIPENo ROA
2a03:ef46::/32RIPENo ROA
2a03:ef47::/32RIPENo ROA

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.