Network · data from 2026-11-12

AS272476 INFOTOTAL TELECOM

Registry name: AS272476 - INFOTOTAL TELECOM, BR · PeeringDB

0IPv4 routes

3IPv6 routes 0.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS272476, seen from no peer

Announced routes

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


2804:81c8::/33	No ROA	Nonecovered by 2804:81c8::/32	635 100%	69
2804:81c8:8000::/33	No ROA	Nonecovered by 2804:81c8::/32	635 100%	69
2804:81c8::/32	No ROA	Other IRR onlyRADB, TC	635 100%	69

AS-SET

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

ROA: none3
Route object: none2
Route object: RIR1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:81c8::/33	No ROA covers it. Add a ROA for AS272476, maxLength 33.	635 of 636
Route object: none	2804:81c8::/33	No route object for it. A route object for 2804:81c8::/32 with origin AS272476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272476 in the RIR database for the space.	635 of 636
ROA: none	2804:81c8:8000::/33	No ROA covers it. Add a ROA for AS272476, maxLength 33.	635 of 636
Route object: none	2804:81c8:8000::/33	No route object for it. A route object for 2804:81c8::/32 with origin AS272476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272476 in the RIR database for the space.	635 of 636
ROA: none	2804:81c8::/32	No ROA covers it. Add a ROA for AS272476, maxLength 32.	635 of 636
Route object: RIR	2804:81c8::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:81c8::/33

No ROA covers it. Add a ROA for AS272476, maxLength 33.

635 of 636

Route object: none

2804:81c8::/33

No route object for it. A route object for 2804:81c8::/32 with origin AS272476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272476 in the RIR database for the space.

635 of 636

ROA: none

2804:81c8:8000::/33

No ROA covers it. Add a ROA for AS272476, maxLength 33.

635 of 636

Route object: none

2804:81c8:8000::/33

635 of 636

ROA: none

2804:81c8::/32

No ROA covers it. Add a ROA for AS272476, maxLength 32.

635 of 636

Route object: RIR

2804:81c8::/32

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

635 of 636

Route objects not announced

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


45.178.82.0/23	RADB	No ROA

45.178.82.0/23

RADB

No 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.