bgpreport

Network · data from 2026-11-12

AS10922 Better Stack, Inc.

Registry name: BETTERSTACK - Better Stack, Inc., US · PeeringDB

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

Announced routes

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

167.254.228.0/23 Valid Nonecovered by 167.254.228.0/22 670 100% 67
167.254.230.0/23 Valid Nonecovered by 167.254.228.0/22 670 100% 67
195.63.192.0/21 Valid Nonecovered by 195.63.192.0/20 670 100% 67
195.63.200.0/21 Valid Nonecovered by 195.63.192.0/20 670 100% 67
195.63.224.0/20 Valid RIR databaseRIPE 672 100% 67
195.63.208.0/20 Valid RIR databaseRIPE 671 100% 67
167.254.228.0/22 Valid RIR databaseARIN 670 100% 67
195.63.192.0/20 Valid RIR databaseRIPE 670 100% 67
2a0f:1b80::/40 Valid RIR databaseRIPE 636 100% 67
2604:2c20::/40 Valid RIR databaseARIN 634 100% 68
2604:2c20:100::/40 Valid RIR databaseARIN 633 100% 68

AS-SET

AS10922'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 8 are in fix.csv.

  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none167.254.228.0/23No route object for it. A route object for 167.254.228.0/22 with origin AS10922 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10922 in the RIR database for the space.670 of 673
Route object: none167.254.230.0/23No route object for it. A route object for 167.254.228.0/22 with origin AS10922 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10922 in the RIR database for the space.670 of 673
Route object: none195.63.192.0/21No route object for it. A route object for 195.63.192.0/20 with origin AS10922 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10922 in the RIR database for the space.670 of 673
Route object: none195.63.200.0/21No route object for it. A route object for 195.63.192.0/20 with origin AS10922 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10922 in the RIR database for the space.670 of 673

Route objects not announced

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

195.63.192.0/18RIPENo ROA
195.63.240.0/20RIPEValid
2604:2c20::/32ARINValid
2a0f:1b80::/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.