bgpreport

Network · data from 2026-11-12

AS265147 Banda Larga UP

Registry name: AS265147 - UP Fibra, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265147, 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.
143.255.128.0/22 No ROA Other IRR onlyALTDB, RADB, TC 672 100% 67
143.255.128.0/23 No ROA Other IRR onlyRADB 672 100% 67
143.255.128.0/24 No ROA Other IRR onlyRADB 672 100% 67
143.255.129.0/24 No ROA Other IRR onlyRADB 672 100% 67
143.255.130.0/23 No ROA Other IRR onlyRADB 672 100% 67
143.255.130.0/24 No ROA Other IRR onlyRADB 672 100% 67
143.255.131.0/24 No ROA Other IRR onlyRADB 672 100% 67
2804:2b54::/32 No ROA Other IRR onlyALTDB, RADB, TC 636 100% 70
2804:2b54::/33 No ROA Other IRR onlyRADB 636 100% 70
2804:2b54::/34 No ROA Other IRR onlyRADB 636 100% 70
2804:2b54:4000::/34 No ROA Other IRR onlyRADB 636 100% 70
2804:2b54:8000::/34 No ROA Other IRR onlyRADB 636 100% 70
2804:2b54:c000::/34 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS265147: AS-265147. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265147 isn't in the set, or no route object for AS265147 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265147 in itNot covered
AS-265147 ALTDBlists itself further down1 member set in no database: AS-264354 76141,522 Yes 0

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

  • ROA: none13
  • Route object: RIR13
  • AS-SET: missing member1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none143.255.128.0/22No ROA covers it. Add a ROA for AS265147, maxLength 22.672 of 673
Route object: RIR143.255.128.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none143.255.128.0/23No ROA covers it. Add a ROA for AS265147, maxLength 23.672 of 673
Route object: RIR143.255.128.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none143.255.128.0/24No ROA covers it. Add a ROA for AS265147, maxLength 24.672 of 673
Route object: RIR143.255.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none143.255.129.0/24No ROA covers it. Add a ROA for AS265147, maxLength 24.672 of 673
Route object: RIR143.255.129.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none143.255.130.0/23No ROA covers it. Add a ROA for AS265147, maxLength 23.672 of 673
Route object: RIR143.255.130.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none143.255.130.0/24No ROA covers it. Add a ROA for AS265147, maxLength 24.672 of 673
Route object: RIR143.255.130.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none143.255.131.0/24No ROA covers it. Add a ROA for AS265147, maxLength 24.672 of 673
Route object: RIR143.255.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:2b54::/32No ROA covers it. Add a ROA for AS265147, maxLength 32.636 of 636
Route object: RIR2804:2b54::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:2b54::/33No ROA covers it. Add a ROA for AS265147, maxLength 33.636 of 636
Route object: RIR2804:2b54::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:2b54::/34No ROA covers it. Add a ROA for AS265147, maxLength 34.636 of 636
Route object: RIR2804:2b54::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:2b54:4000::/34No ROA covers it. Add a ROA for AS265147, maxLength 34.636 of 636
Route object: RIR2804:2b54:4000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:2b54:8000::/34No ROA covers it. Add a ROA for AS265147, maxLength 34.636 of 636
Route object: RIR2804:2b54:8000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:2b54:c000::/34No ROA covers it. Add a ROA for AS265147, maxLength 34.635 of 636
Route object: RIR2804:2b54:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: missing memberAS-265147AS-265147 (ALTDB) lists AS-264354; no IRR database read has it.

Route objects not announced

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

2804:12d4::/32RADBNo ROA
2804:2b54: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.