bgpreport

Network · data from 2026-11-12

AS28273 AS28273 - Hispamar Satelites S/A

Registry name: AS28273 - Hispamar Satelites S/A, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28273, 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.
201.33.7.0/24 Invalid: maxLength Nonecovered by 201.33.0.0/21 18 3%low visibility 11
201.33.9.0/24 No ROA Other IRR onlyTC 669 99% 67
201.33.10.0/24 No ROA Other IRR onlyTC 669 99% 67
201.33.12.0/24 No ROA Other IRR onlyTC 669 99% 67
201.33.0.0/21 Valid Other IRR onlyTC 673 100% 70
201.33.8.0/24 Valid Other IRR onlyTC 673 100% 70
201.33.14.0/24 Valid Other IRR onlyTC 673 100% 70
201.33.15.0/24 Valid Other IRR onlyTC 672 100% 70

AS-SET

AS28273 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 16 are in fix.csv.

  • ROA: maxLength1
  • ROA: none3
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength201.33.7.0/24ROA 201.33.0.0/21 AS28273 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 201.33.7.0/24.18 of 673
Route object: none201.33.7.0/24No route object for it. A route object for 201.33.0.0/21 with origin AS28273 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28273 in the RIR database for the space.18 of 673
ROA: none201.33.9.0/24No ROA covers it. Add a ROA for AS28273, maxLength 24.669 of 673
Route object: RIR201.33.9.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none201.33.10.0/24No ROA covers it. Add a ROA for AS28273, maxLength 24.669 of 673
Route object: RIR201.33.10.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none201.33.12.0/24No ROA covers it. Add a ROA for AS28273, maxLength 24.669 of 673
Route object: RIR201.33.12.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR201.33.0.0/21Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR201.33.8.0/24Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR201.33.14.0/24Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR201.33.15.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

201.33.0.0/20TCNo ROA
201.33.11.0/24TCNo ROA
201.33.13.0/24TCValid
2a0d:a5c7::/40RIPEInvalid: origin

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.