bgpreport

Network · data from 2026-11-12

AS262803 NETULTRA PROVEDOR DE INTERNET

Registry name: AS262803 - NETULTRA PROVEDOR DE INTERNET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262803, 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:250:c000::/34 No ROA Nonecovered by 2804:250:8000::/33 632 99% 67
186.250.18.0/24 No ROA Other IRR onlyALTDB 672 100% 66
186.250.19.0/24 No ROA Other IRR onlyALTDB 672 100% 66
186.250.22.0/24 No ROA Other IRR onlyALTDB 672 100% 66
186.250.23.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
186.250.16.0/21 No ROA Other IRR onlyALTDB, RADB, TC 671 100% 66
186.250.16.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 66
186.250.20.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 66
186.250.20.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 66
186.250.21.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 66
186.250.16.0/24 No ROA Other IRR onlyALTDB 670 100% 67
186.250.17.0/24 No ROA Other IRR onlyALTDB 670 100% 67
2804:250::/32 No ROA Other IRR onlyALTDB, RADB, TC 636 100% 67
186.250.16.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2
186.250.18.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2
186.250.20.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2
186.250.22.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2

AS-SET

AS262803's PeeringDB record names no 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 36 are in fix.csv.

  • ROA: none17
  • Route object: none1
  • Route object: RIR16
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:250:c000::/34No ROA covers it. Add a ROA for AS262803, maxLength 34.632 of 636
Route object: none2804:250:c000::/34No route object for it. A route object for 2804:250:8000::/33 with origin AS262803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262803 in the RIR database for the space.632 of 636
ROA: none186.250.18.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.672 of 673
Route object: RIR186.250.18.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none186.250.19.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.672 of 673
Route object: RIR186.250.19.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none186.250.22.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.672 of 673
Route object: RIR186.250.22.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none186.250.23.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.672 of 673
Route object: RIR186.250.23.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none186.250.16.0/21No ROA covers it. Add a ROA for AS262803, maxLength 21.671 of 673
Route object: RIR186.250.16.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none186.250.16.0/22No ROA covers it. Add a ROA for AS262803, maxLength 22.671 of 673
Route object: RIR186.250.16.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.250.20.0/22No ROA covers it. Add a ROA for AS262803, maxLength 22.671 of 673
Route object: RIR186.250.20.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.250.20.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.671 of 673
Route object: RIR186.250.20.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.250.21.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.671 of 673
Route object: RIR186.250.21.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.250.16.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.670 of 673
Route object: RIR186.250.16.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none186.250.17.0/24No ROA covers it. Add a ROA for AS262803, maxLength 24.670 of 673
Route object: RIR186.250.17.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none2804:250::/32No ROA covers it. Add a ROA for AS262803, maxLength 32.636 of 636
Route object: RIR2804:250::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none186.250.16.0/23No ROA covers it. Add a ROA for AS262803, maxLength 23.2 of 673
Route object: RIR186.250.16.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
ROA: none186.250.18.0/23No ROA covers it. Add a ROA for AS262803, maxLength 23.2 of 673
Route object: RIR186.250.18.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
ROA: none186.250.20.0/23No ROA covers it. Add a ROA for AS262803, maxLength 23.2 of 673
Route object: RIR186.250.20.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
ROA: none186.250.22.0/23No ROA covers it. Add a ROA for AS262803, maxLength 23.2 of 673
Route object: RIR186.250.22.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:250::/33RADBNo ROA
2804:250:8000::/33RADBNo 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.