bgpreport

Network · data from 2026-11-12

AS209622 upress-drb uPress Inc

Registry name: upress-drb uPress Inc, US · not in PeeringDB

15IPv4 routes 66.7% RPKI valid · 100.0% with a route object
6IPv6 routes 100.0% RPKI valid · 83.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS209622, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS209622, 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.
185.201.148.0/24 No ROA RIR databaseRIPE 673 100% 67
185.201.150.0/24 No ROA RIR databaseRIPE 673 100% 67
185.108.150.0/24 No ROA RIR databaseRIPE 672 100% 67
185.201.149.0/24 No ROA RIR databaseRIPE 672 100% 67
185.108.148.0/23 No ROA RIR databaseRIPE 671 100% 67
2a07:4300:61::/48 Valid None 636 100% 67
88.218.118.0/24 Valid RIR databaseRIPE 673 100% 67
155.117.125.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.131.146.0/24 Valid RIR databaseRIPE 673 100% 66
185.201.151.0/24 Valid RIR databaseRIPE 673 100% 67
194.231.220.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
5.154.240.0/24 Valid RIR databaseRIPE 672 100% 67
88.218.116.0/24 Valid RIR databaseRIPE 671 100% 67
88.218.117.0/24 Valid RIR databaseRIPE 671 100% 67
88.218.119.0/24 Valid RIR databaseRIPE 671 100% 67
185.131.147.0/24 Valid RIR databaseRIPE 671 100% 66
2a07:4300:972::/48 Valid RIR databaseRIPE 636 100% 67
2a07:4300:1611::/48 Valid RIR databaseRADB, RIPE 635 100% 67
2a07:4300:31::/48 Valid RIR databaseRIPE 634 100% 67
2a07:4300:1609::/48 Valid RIR databaseRIPE 634 100% 68
2a07:4300:1610::/48 Valid RIR databaseRIPE 634 100% 68

AS-SET

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

  • ROA: none5
  • Route object: none1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none185.201.148.0/24No ROA covers it. Add a ROA for AS209622, maxLength 24.673 of 673
ROA: none185.201.150.0/24No ROA covers it. Add a ROA for AS209622, maxLength 24.673 of 673
ROA: none185.108.150.0/24No ROA covers it. Add a ROA for AS209622, maxLength 24.672 of 673
ROA: none185.201.149.0/24No ROA covers it. Add a ROA for AS209622, maxLength 24.672 of 673
ROA: none185.108.148.0/23No ROA covers it. Add a ROA for AS209622, maxLength 23.671 of 673
Route object: none2a07:4300:61::/48No route object for it. Add a route object with origin AS209622 in the RIR database for the space.636 of 636

Route objects not announced

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

88.218.116.0/22RIPENo ROA
185.108.148.0/22RIPENo ROA
185.108.148.0/24RIPENo ROA
185.108.149.0/24RIPENo ROA
185.108.151.0/24RIPENo ROA
185.201.148.0/22RIPENo ROA
185.201.148.0/23RIPENo 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.