Network · data from 2026-11-12

AS273774 MAXDATA SISTEMAS LTDA

Registry name: AS273774 - MAXDATA SISTEMAS LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 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 AS273774, seen from no peer

Announced routes

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


45.177.250.0/23	Valid	Other IRR onlyRADB, TC	673 100%	67
45.177.248.0/23	Valid	Other IRR onlyRADB, TC	672 100%	67
45.177.248.0/22	Valid	Other IRR onlyTC	667 99%	67
2804:8c04::/32	Valid	Other IRR onlyRADB, TC	630 99%	67
45.177.250.0/24	Valid	Other IRR onlyTC	203 30%	56
45.177.251.0/24	Valid	Other IRR onlyTC	203 30%	56
45.177.248.0/24	Valid	Other IRR onlyTC	202 30%	56
45.177.249.0/24	Valid	Other IRR onlyTC	202 30%	56

AS-SET

AS273774'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 8 are in fix.csv.

Route object: RIR8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.177.250.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	673 of 673
Route object: RIR	45.177.248.0/23	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.177.248.0/22	Route object only in TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:8c04::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	630 of 636
Route object: RIR	45.177.250.0/24	Route object only in TC. Add it in the RIR database for the space.	203 of 673
Route object: RIR	45.177.251.0/24	Route object only in TC. Add it in the RIR database for the space.	203 of 673
Route object: RIR	45.177.248.0/24	Route object only in TC. Add it in the RIR database for the space.	202 of 673
Route object: RIR	45.177.249.0/24	Route object only in TC. Add it in the RIR database for the space.	202 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.177.250.0/23

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

673 of 673

Route object: RIR

45.177.248.0/23

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

672 of 673

Route object: RIR

45.177.248.0/22

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

667 of 673

Route object: RIR

2804:8c04::/32

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

630 of 636

Route object: RIR

45.177.250.0/24

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

203 of 673

Route object: RIR

45.177.251.0/24

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

203 of 673

Route object: RIR

45.177.248.0/24

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

202 of 673

Route object: RIR

45.177.249.0/24

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

202 of 673

Route objects not announced

Every route object with origin AS273774 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.