bgpreport

Network · data from 2026-11-12

AS272426 AS272426 - INTERMAX SERVICOS DE COMUNICACAO LTDA

Registry name: AS272426 - INTERMAX SERVICOS DE COMUNICACAO LTDA, BR · not in PeeringDB

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

Announced routes

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

170.84.255.0/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.1/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.2/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.3/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.4/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.5/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.6/32 Invalid: maxLength Nonecovered by 170.84.255.0/24 0 0%low visibility 1
170.84.255.0/24 Valid Other IRR onlyTC 670 100% 66
201.131.64.0/24 Valid Other IRR onlyTC 670 100% 66
45.169.252.0/24 Valid Other IRR onlyTC 669 99% 67
200.3.114.0/24 Valid Other IRR onlyTC 668 99% 67

AS-SET

AS272426 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 19 are in fix.csv.

  • ROA: maxLength7
  • Route object: none7
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength170.84.255.0/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.0/32.0 of 673
Route object: none170.84.255.0/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
ROA: maxLength170.84.255.1/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.1/32.0 of 673
Route object: none170.84.255.1/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
ROA: maxLength170.84.255.2/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.2/32.0 of 673
Route object: none170.84.255.2/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
ROA: maxLength170.84.255.3/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.3/32.0 of 673
Route object: none170.84.255.3/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
ROA: maxLength170.84.255.4/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.4/32.0 of 673
Route object: none170.84.255.4/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
ROA: maxLength170.84.255.5/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.5/32.0 of 673
Route object: none170.84.255.5/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
ROA: maxLength170.84.255.6/32ROA 170.84.255.0/24 AS272426 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 170.84.255.6/32.0 of 673
Route object: none170.84.255.6/32No route object for it. A route object for 170.84.255.0/24 with origin AS272426 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272426 in the RIR database for the space.0 of 673
Route object: RIR170.84.255.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR201.131.64.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.169.252.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR200.3.114.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

2804:8104::/32RADB, TCValid

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.