Network · data from 2026-11-12

AS265337 SYNDIGITAL TELECOMUNICACOES LTDA

Registry name: AS265337 - SYNDIGITAL TELECOMUNICACOES LTDA, BR · PeeringDB

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

0Route objects not announced registered with origin AS265337, seen from no peer

Announced routes

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


168.181.140.0/22	Valid	Other IRR onlyNTTCOM, RADB, TC	667 99%	67
168.181.140.0/23	Valid	Other IRR onlyRADB, TC	666 99%	67
168.181.142.0/23	Valid	Other IRR onlyRADB, TC	666 99%	67
2804:2e4c::/32	Valid	Other IRR onlyRADB, TC	632 99%	67
2804:2e4c::/33	Valid	Other IRR onlyTC	631 99%	67
2804:2e4c:8000::/33	Valid	Other IRR onlyTC	631 99%	67

AS-SET

PeeringDB's irr_as_set for AS265337: TC::AS265337:AS-SYNDIGITAL. 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 (AS265337 isn't in the set, or no route object for AS265337 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	AS265337 in it	Not covered
TC::AS265337:AS-SYNDIGITAL	TC	2	3	9	Yes	0

Name

Database

ASNs

Sets

Route objects

AS265337 in it

Not covered

TC::AS265337:AS-SYNDIGITAL

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

Route object: RIR6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	168.181.140.0/22	Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	168.181.140.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	666 of 673
Route object: RIR	168.181.142.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	666 of 673
Route object: RIR	2804:2e4c::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	632 of 636
Route object: RIR	2804:2e4c::/33	Route object only in TC. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:2e4c:8000::/33	Route object only in TC. Add it in the RIR database for the space.	631 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

168.181.140.0/22

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

667 of 673

Route object: RIR

168.181.140.0/23

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

666 of 673

Route object: RIR

168.181.142.0/23

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

666 of 673

Route object: RIR

2804:2e4c::/32

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

632 of 636

Route object: RIR

2804:2e4c::/33

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

631 of 636

Route object: RIR

2804:2e4c:8000::/33

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

631 of 636

Route objects not announced

Every route object with origin AS265337 is announced.

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.