bgpreport

Network · data from 2026-11-12

AS212628 ARTRUBY

Registry name: AS-ARTRUBY ARTRUBY PTE. LTD., SG · PeeringDB

15IPv4 routes 86.7% RPKI valid · 86.7% with a route object
5IPv6 routes 80.0% RPKI valid · 20.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 6 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS212628, seen from no peer

Announced routes

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

2001:550:2004::/48 No ROA None 635 100% 67
38.95.160.0/24 No ROA None 1 0%low visibility 1
154.57.39.0/24 No ROA None 1 0%low visibility 1
2a13:aac4:f052::/48 Valid Nonecovered by 2a13:aac4:f050::/44 632 99% 67
2a13:aac4:f055::/48 Valid Nonecovered by 2a13:aac4:f050::/44 324 51% 65
2a13:aac4:f051::/48 Valid Nonecovered by 2a13:aac4:f050::/44 2 0%low visibility 3
66.51.67.0/24 Valid RIR databaseRIPE 673 100% 67
66.51.74.0/24 Valid RIR databaseRIPE 673 100% 67
66.51.77.0/24 Valid RIR databaseRIPE 672 100% 67
66.51.68.0/24 Valid RIR databaseRIPE 671 100% 67
66.51.73.0/24 Valid RIR databaseRIPE 671 100% 68
66.51.69.0/24 Valid RIR databaseRIPE 670 100% 68
66.51.66.0/24 Valid RIR databaseRIPE 669 99% 67
66.51.64.0/24 Valid RIR databaseRIPE 667 99% 67
66.51.65.0/24 Valid RIR databaseRIPE 667 99% 67
66.51.70.0/24 Valid RIR databaseRIPE 667 99% 67
66.51.71.0/24 Valid RIR databaseRIPE 667 99% 67
66.51.72.0/24 Valid RIR databaseRIPE 664 99% 67
2a13:aac4:f050::/44 Valid RIR databaseRIPE 3 0%low visibility 4
66.51.75.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS212628's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none3
  • Route object: none6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2001:550:2004::/48No ROA covers it. Add a ROA for AS212628, maxLength 48.635 of 636
Route object: none2001:550:2004::/48No route object for it. Add a route object with origin AS212628 in the RIR database for the space.635 of 636
ROA: none38.95.160.0/24No ROA covers it. Add a ROA for AS212628, maxLength 24.1 of 673
Route object: none38.95.160.0/24No route object for it. Add a route object with origin AS212628 in the RIR database for the space.1 of 673
ROA: none154.57.39.0/24No ROA covers it. Add a ROA for AS212628, maxLength 24.1 of 673
Route object: none154.57.39.0/24No route object for it. Add a route object with origin AS212628 in the RIR database for the space.1 of 673
Route object: none2a13:aac4:f052::/48No route object for it. A route object for 2a13:aac4:f050::/44 with origin AS212628 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212628 in the RIR database for the space.632 of 636
Route object: none2a13:aac4:f055::/48No route object for it. A route object for 2a13:aac4:f050::/44 with origin AS212628 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212628 in the RIR database for the space.324 of 636
Route object: none2a13:aac4:f051::/48No route object for it. A route object for 2a13:aac4:f050::/44 with origin AS212628 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212628 in the RIR database for the space.2 of 636

Route objects not announced

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

64.118.144.0/22RIPEValid
66.51.64.0/20RIPEValid
154.16.242.0/23RADBValid
216.236.1.0/24RIPEValid

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.