Network · data from 2026-11-12

AS273612 FABWEB

Registry name: AS273612 - FABWEB SERVICOS DE INTERNET LTDA, BR · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

3Route objects not announced registered with origin AS273612, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273612, 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:8990:1000::/48	Valid	Nonecovered by 2804:8990::/33	636 100%	67
2804:8990:2000::/48	Valid	Nonecovered by 2804:8990::/33	636 100%	67
2804:8990:8000::/48	Valid	Nonecovered by 2804:8990:8000::/33	636 100%	67
50.114.62.0/24	Valid	RIR databaseARIN, RADB	671 100%	67
151.243.0.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
166.0.186.0/24	Valid	RIR databaseARIN, RADB	670 100%	67

AS-SET

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

Route object: none3
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:8990:1000::/48	No route object for it. A route object for 2804:8990::/33 with origin AS273612 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273612 in the RIR database for the space.	636 of 636
Route object: none	2804:8990:2000::/48	No route object for it. A route object for 2804:8990::/33 with origin AS273612 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273612 in the RIR database for the space.	636 of 636
Route object: none	2804:8990:8000::/48	No route object for it. A route object for 2804:8990:8000::/33 with origin AS273612 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273612 in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:8990:1000::/48

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

636 of 636

Route object: none

2804:8990:2000::/48

636 of 636

Route object: none

2804:8990:8000::/48

No route object for it. A route object for 2804:8990:8000::/33 with origin AS273612 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273612 in the RIR database for the space.

636 of 636

Route objects not announced

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


2804:8990::/32	RADB, TC	Valid
2804:8990::/33	RADB	Valid
2804:8990:8000::/33	RADB	Valid

2804:8990::/32

RADB, TC

Valid

2804:8990::/33

RADB

Valid

2804:8990:8000::/33

RADB

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.