bgpreport

Network · data from 2026-11-12

AS263527 SERRA GERAL SOLUCOES PARA INTERNET

Registry name: AS263527 - SERRA GERAL SOLUCOES PARA INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263527, 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:134c:8100::/40 No ROA Nonecovered by 2804:134c::/32 632 99% 67
2804:134c:8300::/40 No ROA Nonecovered by 2804:134c::/32 632 99% 67
45.171.78.0/24 No ROA Other IRR onlyRADB, TC 666 99% 67
191.253.40.0/21 No ROA Other IRR onlyRADB, TC 666 99% 67
191.253.47.0/24 No ROA Other IRR onlyTC 662 98% 66
2804:134c::/32 No ROA Other IRR onlyRADB, TC 630 99% 67

AS-SET

PeeringDB's irr_as_set for AS263527: AS263527:AS-ANNOUNCEMENTS. 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 (AS263527 isn't in the set, or no route object for AS263527 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 objectsAS263527 in itNot covered
AS263527:AS-ANNOUNCEMENTS TClists itself further down3 member sets in no database: AS-RMS, AS-SNT-28604, AS264461:AS-ANNOUNCEMENTS 5227604 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 22 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • AS-SET: missing member3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2804:134c:8100::/40No ROA covers it. Add a ROA for AS263527, maxLength 40.632 of 636
Route object: none2804:134c:8100::/40No route object for it. A route object for 2804:134c::/32 with origin AS263527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263527 in the RIR database for the space.632 of 636
ROA: none2804:134c:8300::/40No ROA covers it. Add a ROA for AS263527, maxLength 40.632 of 636
Route object: none2804:134c:8300::/40No route object for it. A route object for 2804:134c::/32 with origin AS263527 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263527 in the RIR database for the space.632 of 636
ROA: none45.171.78.0/24No ROA covers it. Add a ROA for AS263527, maxLength 24.666 of 673
Route object: RIR45.171.78.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none191.253.40.0/21No ROA covers it. Add a ROA for AS263527, maxLength 21.666 of 673
Route object: RIR191.253.40.0/21Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none191.253.47.0/24No ROA covers it. Add a ROA for AS263527, maxLength 24.662 of 673
Route object: RIR191.253.47.0/24Route object only in TC. Add it in the RIR database for the space.662 of 673
ROA: none2804:134c::/32No ROA covers it. Add a ROA for AS263527, maxLength 32.630 of 636
Route object: RIR2804:134c::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
AS-SET: missing memberAS263527:AS-ANNOUNCEMENTSAS263527:AS-ANNOUNCEMENTS (TC) lists AS-RMS; no IRR database read has it.
AS-SET: missing memberAS263527:AS-ANNOUNCEMENTSAS263527:AS-ANNOUNCEMENTS (TC) lists AS-SNT-28604; no IRR database read has it.
AS-SET: missing memberAS263527:AS-ANNOUNCEMENTSAS263527:AS-ANNOUNCEMENTS (TC) lists AS264461:AS-ANNOUNCEMENTS; no IRR database read has it.

Route objects not announced

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

191.253.40.0/24TCNo ROA
191.253.41.0/24TCNo ROA
191.253.42.0/24TCNo ROA
191.253.43.0/24TCNo ROA
191.253.44.0/24TCNo ROA
191.253.45.0/24TCNo ROA
191.253.46.0/24TCNo 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.