bgpreport

Network · data from 2026-11-12

AS271194 online telecomunicações eirele

Registry name: AS271194 - online telecomunicacoes eirele, BR · PeeringDB

7IPv4 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
2Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS271194, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271194, 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.
179.49.148.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
179.49.148.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
179.49.149.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
179.49.150.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
179.49.151.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
2804:77b4::/32 Valid Other IRR onlyRADB, TC 636 100% 69
2804:77b4::/33 Valid Other IRR onlyRADB, TC 635 100% 67
2804:77b4:8000::/33 Valid Other IRR onlyRADB, TC 635 100% 67
179.49.148.0/23 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
179.49.150.0/23 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

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

NameDatabaseASNsSets Route objectsAS271194 in itNot covered
AS271194 A single AS number, not a set: AS271194 (this network), 11 route objects.

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

  • Route object: RIR10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR179.49.148.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR179.49.148.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR179.49.149.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR179.49.150.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR179.49.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:77b4::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:77b4::/33Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:77b4:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR179.49.148.0/23Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR179.49.150.0/23Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:268c::/32RADBNo 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.