bgpreport

Network · data from 2026-11-12

AS263947 Tavares & Repolho

Registry name: AS263947 - VirtualSpace Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263947, 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.
138.255.14.0/24 No ROA Other IRR onlyALTDB 670 100% 67
138.255.12.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 66
138.255.13.0/24 Valid Other IRR onlyRADB 671 100% 66
138.255.15.0/24 Valid Other IRR onlyALTDB, RADB 669 99% 67
2804:2834:c000::/34 Valid Other IRR onlyRADB 636 100% 67
2804:2834::/34 Valid Other IRR onlyRADB 634 100% 67
2804:2834:4000::/34 Valid Other IRR onlyRADB 634 100% 67
2804:2834:8000::/34 Valid Other IRR onlyRADB 634 100% 67
2804:2834::/32 Valid Other IRR onlyALTDB, RADB, TC 2 0%low visibility 2
138.255.12.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS263947'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 13 are in fix.csv.

  • ROA: none1
  • Route object: RIR10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none138.255.14.0/24No ROA covers it. Add a ROA for AS263947, maxLength 24.670 of 673
Route object: RIR138.255.14.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR138.255.12.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.255.13.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.255.15.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:2834:c000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2834::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2834:4000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2834:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2834::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.2 of 636
Route object: RIR138.255.12.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

138.255.12.0/22ALTDB, RADB, TCNo ROA
138.255.14.0/23ALTDB, RADBNo 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.