Network · data from 2026-11-12

AS61752 BATISTA PEREIRA INFORMATICA LTDA.

Registry name: AS61752 - BATISTA PEREIRA INFORMATICA LTDA., BR · PeeringDB

1IPv4 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

6Route objects not announced registered with origin AS61752, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61752, 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.


131.100.12.0/22	Valid	Other IRR onlyTC	666 99%	67
2804:1bd0::/32	Valid	Other IRR onlyTC	634 100%	67
2804:1bd0::/33	Valid	Other IRR onlyTC	634 100%	67
2804:1bd0:8000::/33	Valid	Other IRR onlyTC	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS61752: AS-61752. 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 (AS61752 isn't in the set, or no route object for AS61752 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.

Name	Database	ASNs	Sets	Route objects	AS61752 in it	Not covered
AS-61752	TC	1	1	10	Yes	0

Name

Database

ASNs

Sets

Route objects

AS61752 in it

Not covered

AS-61752

Yes

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

Route object: RIR4
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	131.100.12.0/22	Route object only in TC. Add it in the RIR database for the space.	666 of 673
Route object: RIR	2804:1bd0::/32	Route object only in TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:1bd0::/33	Route object only in TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:1bd0:8000::/33	Route object only in TC. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

131.100.12.0/22

Route object only in TC. Add it in the RIR database for the space.

666 of 673

Route object: RIR

2804:1bd0::/32

Route object only in TC. Add it in the RIR database for the space.

634 of 636

Route object: RIR

2804:1bd0::/33

Route object only in TC. Add it in the RIR database for the space.

634 of 636

Route object: RIR

2804:1bd0:8000::/33

Route object only in TC. Add it in the RIR database for the space.

634 of 636

Route objects not announced

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


131.100.12.0/23	TC	Valid
131.100.12.0/24	TC	Valid
131.100.13.0/24	TC	Valid
131.100.14.0/23	TC	Valid
131.100.14.0/24	TC	Valid
131.100.15.0/24	TC	Valid

131.100.12.0/23

Valid

131.100.12.0/24

Valid

131.100.13.0/24

Valid

131.100.14.0/23

Valid

131.100.14.0/24

Valid

131.100.15.0/24

Valid

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.