Network · data from 2026-11-12
AS54971 BROWN-TECHNOLOGIES - Brown Technologies, LLC
Registry name: BROWN-TECHNOLOGIES - Brown Technologies, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54971, 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.
| 198.102.29.0/24 | Invalid: origin | Other origin only | 73 11% |
| 167.88.211.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 155.103.124.0/24 | Valid | Nonecovered by 155.103.124.0/23 | 673 100% |
| 155.103.125.0/24 | Valid | Nonecovered by 155.103.124.0/23 | 673 100% |
AS-SET
AS54971 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 9 are in fix.csv.
- ROA: origin2
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 198.102.29.0/24 | ROAs covering it name AS1097, not AS54971. If AS54971 should announce it, add a ROA for AS54971. |
| Route object: none | 198.102.29.0/24 | Route objects for it name AS1097. Add a route object with origin AS54971 in the RIR database for the space. |
| ROA: origin | 167.88.211.0/24 | ROAs covering it name AS1097, AS403090, not AS54971. If AS54971 should announce it, add a ROA for AS54971. |
| Route object: none | 167.88.211.0/24 | Route objects for it name AS1097, AS403090. Add a route object with origin AS54971 in the RIR database for the space. |
| Route object: none | 155.103.124.0/24 | No route object for it. A route object for 155.103.124.0/23 with origin AS54971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54971 in the RIR database for the space. |
| Route object: none | 155.103.125.0/24 | No route object for it. A route object for 155.103.124.0/23 with origin AS54971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54971 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54971 whose prefix no peer sees AS54971 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 155.103.124.0/23 | ARIN | Valid |
| 192.240.148.0/23 | ARIN, RADB | No ROA |
| 192.240.149.0/24 | RADB | No 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.