bgpreport

Network · data from 2026-11-12

AS268989 AS268989 - MULTTV CONSULTORIA E LOCACOES DE EQUIPAMENTOS S.A.

Registry name: AS268989 - MULTTV CONSULTORIA E LOCACOES DE EQUIPAMENTOS S.A., BR · not in PeeringDB

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

Announced routes

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

2804:1f46:ffff::/48 No ROA Nonecovered by 2804:1f46:8000::/33 636 100% 67
2804:1f46::/48 No ROA Nonecovered by 2804:1f46::/33 632 99% 67
45.177.168.0/24 No ROA Other IRR onlyTC 672 100% 66
45.177.170.0/23 No ROA Other IRR onlyTC 672 100% 67
45.177.170.0/24 No ROA Other IRR onlyTC 672 100% 67
45.177.169.0/24 No ROA Other IRR onlyTC 671 100% 66
45.177.171.0/24 No ROA Other IRR onlyTC 2 0%low visibility 2

AS-SET

AS268989 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 20 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2804:1f46:ffff::/48No ROA covers it. Add a ROA for AS268989, maxLength 48.636 of 636
Route object: none2804:1f46:ffff::/48No route object for it. A route object for 2804:1f46:8000::/33 with origin AS268989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268989 in the RIR database for the space.636 of 636
ROA: none2804:1f46::/48No ROA covers it. Add a ROA for AS268989, maxLength 48.632 of 636
Route object: none2804:1f46::/48No route object for it. A route object for 2804:1f46::/33 with origin AS268989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268989 in the RIR database for the space.632 of 636
ROA: none45.177.168.0/24No ROA covers it. Add a ROA for AS268989, maxLength 24.672 of 673
Route object: RIR45.177.168.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none45.177.170.0/23No ROA covers it. Add a ROA for AS268989, maxLength 23.672 of 673
Route object: RIR45.177.170.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none45.177.170.0/24No ROA covers it. Add a ROA for AS268989, maxLength 24.672 of 673
Route object: RIR45.177.170.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none45.177.169.0/24No ROA covers it. Add a ROA for AS268989, maxLength 24.671 of 673
Route object: RIR45.177.169.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.177.171.0/24No ROA covers it. Add a ROA for AS268989, maxLength 24.2 of 673
Route object: RIR45.177.171.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.177.168.0/22RADB, TCNo ROA
45.177.168.0/23TCNo ROA
2801:80:3590::/48RADBNo ROA
2804:1f46::/32RADB, TCNo ROA
2804:1f46::/33TCNo ROA
2804:1f46:8000::/33TCNo 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.