bgpreport

Network · data from 2026-11-12

AS273633 AS273633 - BOX TELECOM

Registry name: AS273633 - BOX TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273633, 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.
45.173.49.0/24 Invalid: origin None 71 11% 35
2804:89e4::/34 No ROA Nonecovered by 2804:89e4::/33 635 100% 67
2804:89e4:4000::/34 No ROA Nonecovered by 2804:89e4::/33 635 100% 67
2804:89e4:8000::/34 No ROA Nonecovered by 2804:89e4:8000::/33 635 100% 67
2804:89e4:c000::/34 No ROA Nonecovered by 2804:89e4:8000::/33 635 100% 67
2804:89e4::/32 No ROA Other IRR onlyTC 635 100% 67
2804:89e4::/33 No ROA Other IRR onlyTC 635 100% 67
2804:89e4:8000::/33 No ROA Other IRR onlyTC 635 100% 67

AS-SET

AS273633 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: origin1
  • ROA: none7
  • Route object: none5
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: origin45.173.49.0/24ROAs covering it name AS268793, not AS273633. If AS273633 should announce it, add a ROA for AS273633.71 of 673
Route object: none45.173.49.0/24No route object for it. Add a route object with origin AS273633 in the RIR database for the space.71 of 673
ROA: none2804:89e4::/34No ROA covers it. Add a ROA for AS273633, maxLength 34.635 of 636
Route object: none2804:89e4::/34No route object for it. A route object for 2804:89e4::/33 with origin AS273633 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273633 in the RIR database for the space.635 of 636
ROA: none2804:89e4:4000::/34No ROA covers it. Add a ROA for AS273633, maxLength 34.635 of 636
Route object: none2804:89e4:4000::/34No route object for it. A route object for 2804:89e4::/33 with origin AS273633 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273633 in the RIR database for the space.635 of 636
ROA: none2804:89e4:8000::/34No ROA covers it. Add a ROA for AS273633, maxLength 34.635 of 636
Route object: none2804:89e4:8000::/34No route object for it. A route object for 2804:89e4:8000::/33 with origin AS273633 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273633 in the RIR database for the space.635 of 636
ROA: none2804:89e4:c000::/34No ROA covers it. Add a ROA for AS273633, maxLength 34.635 of 636
Route object: none2804:89e4:c000::/34No route object for it. A route object for 2804:89e4:8000::/33 with origin AS273633 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273633 in the RIR database for the space.635 of 636
ROA: none2804:89e4::/32No ROA covers it. Add a ROA for AS273633, maxLength 32.635 of 636
Route object: RIR2804:89e4::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:89e4::/33No ROA covers it. Add a ROA for AS273633, maxLength 33.635 of 636
Route object: RIR2804:89e4::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:89e4:8000::/33No ROA covers it. Add a ROA for AS273633, maxLength 33.635 of 636
Route object: RIR2804:89e4:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS273633 is announced.

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.