bgpreport

Network · data from 2026-11-12

AS213920 FONSECA

Registry name: FONSECA FONSECA ALVES TECNOLOGIA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213920, 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.
2a0c:b641:3f::/48 Valid Other IRR onlyRADB 635 100% 67
2a0c:b641:3e::/48 Valid Other IRR onlyRADB 634 100% 69
143.20.0.0/24 Valid RIR databaseRADB, RIPE 671 100% 70
185.219.189.0/24 Valid RIR databaseRADB, RIPE 671 100% 70
178.132.198.0/24 Valid RIR databaseRADB, RIPE 670 100% 70
151.242.142.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
185.225.22.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
151.242.25.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
2a0c:b641:30::/44 Valid RIR databaseRADB, RIPE 636 100% 67

AS-SET

AS213920'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 3 are in fix.csv.

  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR2a0c:b641:3f::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a0c:b641:3e::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2a13:9500:141::/48RIPEInvalid: origin

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.